When an agent connects to Delta, it sees exactly four tools, and they never change:
| Tool | Function |
|---|---|
start-here | The briefing the agent reads once per session: how Delta works and what the rules are. |
discover-abilities | Lists what the site can do right now, filtered by search or category. |
get-ability-info | Returns the exact instructions for one ability before use. |
execute-ability | Performs the work. Pages, templates, design, and media all run through this one tool. |
Everything else is an ability: one named operation, such as delta/create-page or delta/update-tokens. There are more than two hundred of them, organized in categories, and the number changes with the plugins you run. When the agent creates a page, it calls execute-ability with delta/create-page inside.
This design lets abilities come, go, or be switched off without breaking the connection. Install WooCommerce and about 70 store abilities appear; deactivate it and they disappear. Some plugins publish abilities of their own, and the agent runs those through the same four tools. See What integrations are. No reconnection is needed in either case.
We kept the tool list at four on purpose. An MCP client loads the description of every tool into the agent’s context when it connects, so a hundred tools would spend that context before any work started. With four tools, the agent reads an ability’s schema only when it is about to use it.
Enabling and disabling abilities
Every ability except the four tools can be disabled on the Abilities screen, under Delta → Agent. A disabled ability still appears in the agent’s list, marked as disabled, and refuses to run with a clear error. Changes apply immediately.
These controls are human-only. An agent cannot enable its own abilities, create its own tokens, or lift its own restrictions. Those controls exist only in your wp-admin.
For developers: every list ability takes perPage and ids, and its answer says the perPage it used.
Related: Skills, rules, and guardrails · An ability fails