Start here
MarkdownWho you are, how things are done in Dakso, and the door to every other tool.
whoami
Section titled “whoami”Who am I · Read only · Listed to the agent from the start
Who this connection is: user, organization, role, what it is allowed to do and which tool sets it sees. Call it first, before anything else. Returns no secrets.
No arguments.
dakso_guide
Section titled “dakso_guide”Read a Dakso guide · Read only · Listed to the agent from the start
How things are done well in Dakso: the method, the pitfalls and worked examples for each topic (flows, tools, CRM, campaigns, channels, queues…). Read the guide of a topic BEFORE changing anything in it. Guides are public documentation; they contain no organization data.
| Argument | Type | Required | Description |
|---|---|---|---|
section |
string | No | Section title or reference/<name> from the guide’s index. Omit to get the guide (short ones come whole; long ones return the introduction and the index). |
topic |
string | No | Guide to read, e.g. “flows”. Omit to list the topics. |
dakso_explore
Section titled “dakso_explore”Explore Dakso capabilities · Read only · Listed to the agent from the start
Find what Dakso can do beyond the tools you see listed. Without arguments: the domains.
With domain: its tools, one line each. With query: the best matching tools. With tools:
the full description and argument schema of those tools, and how to call each one (directly,
with dakso_read, or with dakso_change). Call it before saying something cannot be done.
| Argument | Type | Required | Description |
|---|---|---|---|
domain |
string | No | Domain id to list its tools. Omit to list the domains. |
query |
string | No | Keywords of what you need, e.g. “whatsapp template” or “plantillas”. |
tools |
array | No | Tool names to get their full description and arguments (max 12). |
dakso_read
Section titled “dakso_read”Run a read-only Dakso tool · Read only · Listed to the agent from the start
Run a read-only tool that is not in your tool list. Get its name and arguments from dakso_explore first. Permissions are the same as calling the tool directly.
| Argument | Type | Required | Description |
|---|---|---|---|
tool |
string | Yes | Name of a read-only tool, as returned by dakso_explore. |
args |
object | No | The tool’s arguments, as an object. |
dakso_change
Section titled “dakso_change”Run a Dakso tool that changes data · Changes data · can overwrite or remove · Listed to the agent from the start
Run a tool that creates, edits, publishes or deletes and is not in your tool list. Get its name and arguments from dakso_explore first, and read the guide of its topic. Tell the user which tool you are running and why. Permissions, confirmations and limits are the same as calling the tool directly. Tools that send messages or spend credits are not run from here: they are always in your tool list under their own name.
| Argument | Type | Required | Description |
|---|---|---|---|
descripcion |
string | Yes | One short sentence, in the user’s language, saying what you are doing and why. It is recorded in the organization’s activity log. |
tool |
string | Yes | Name of the tool, as returned by dakso_explore. |
args |
object | No | The tool’s arguments, as an object. |