The host's advertised tool schema is the executable contract for your installed version. Product tools use the indra. prefix. Provider methods are discovered through indra.actions and dispatched through indra.action; they are not all separate top-level MCP tools.
Local tools
| Tool | Required arguments | Optional arguments | Returns |
|---|---|---|---|
indra.search |
sql |
params, timeoutMs |
Read-only SQL result or error |
indra.actions |
None | source, method, query, resource, limit, cursor, profile |
Shared Action names, provider catalog, or selected method schema |
indra.action |
name, params |
None at the outer level | The selected Action's result |
indra.manage |
what |
about, limit, offset, id, enabled |
Requested management state |
indra.instruction |
None; pass {} |
None | Installed operating instructions and available handbook copy |
indra.handbook |
None; pass {} |
None | Handbook and available freshness metadata |
indra.update |
operation |
version, confirmationToken for apply |
Update check or application result |
params in indra.search is an array of scalar SQL values. params in indra.action is an object shaped for the selected Action. Do not interchange them.
Discover, inspect, execute
Call indra.actions with a source:
{"source":"google-drive"}
Then inspect an actual returned method:
{"source":"google-drive","method":"<returned-method-name>"}
Call indra.action using its reviewed schema:
{
"name": "connector.invoke",
"params": {
"source": "google-drive",
"method": "<returned-method-name>",
"input": {"params": {}}
}
}
Fill input.params with the method's required fields. Add body or media only where that method accepts them. A fixed shared Action such as connector.read uses its own name and params; see Shared Actions.
An actions call with no source returns shared Action names. It is not a global search across all app content. Catalog filtering and pagination depend on the selected provider.
Management queries
what |
Use |
|---|---|
sources |
Current source states, including pending setup; optional exact about source |
onboarding |
Current Actions/read readiness without starting another pass |
startup |
Latest automatic connection attempt |
status |
Sources, fleet state, and active process information |
plugins |
Installed components; optional text about, limit 1–50, nonnegative offset |
vault |
Vault identity and stored source counts |
execution |
Durable business receipt; pass its actual ID in about |
plugin.set-enabled |
Change an observed source plugin id with `enabled:true |
For plugins, follow the returned nextOffset until it is null when a complete inventory is needed. The latest startup attempt may omit sources completed earlier; use sources or onboarding for the current picture.
Local Cloud tools
Remote tools are limited by the connection's current grant:
| Granted capability | Tool availability |
|---|---|
| Vault read | indra.search and selected-page indra.read |
| Action discovery | indra.actions and read management |
| Action execution | indra.action and supported source enablement |
| An authorized product capability | indra.instruction and indra.handbook |
Ordinary local MCP uses connector.read through indra.action. It does not expose the remote indra.read tool. Remote indra.read accepts source and an optional bounded request, retaining only the returned page for later Vault search. Remote MCP does not expose indra.update.
Read errors and freshness
Product failures return err and MCP marks the call as an error. Provider results can also contain operation-specific status or errors; inspect them before declaring success.
Where handbook refresh is installed, documentation identifies its version, SHA-256, source (web, cache, or bundled), check time, and stale state. An offline copy remains useful, but documentation does not add missing tools or grant account access. See Updates.