Tools, workflows, and databases

Tool namespacing

Every tool is namespaced so calls route to the right source: <connector>__<tool> for an MCP server (e.g. slack__send_message), <source>__<tool> for a database source, and cmp__<id> for a composite workflow.

Composite workflows

A composite bundles several tool calls into one tool the agent invokes once. Steps run deterministically (no extra LLM round-trips) and can template values from the input and earlier steps. The whole workflow is one audited call.

Databases as tools

Connect a SQL-over-HTTP source and the gateway generates curated, bounded tools (list/read/create/update) per table - governed by the same RBAC, column rules, and audit as any MCP tool. The gateway never holds a service-role key.

Per-tool config

• description: override the prompt agents see for a tool.
• blockInput: input fields hidden from the schema and stripped from calls.
• redactOutput: result fields removed from responses.
• fieldDescriptions: per-field description overrides shown to agents.