export declare const TOOLS_PROMPT = "## Tool Guidance\n\n### Purpose\n\nUse this to give the target agent callable capabilities through MCP servers,\nworkflows, nodes, custom code tools, or provider tools.\n\n### Workflow\n\nUse this guidance before calling `resolve_integration`, `search_nodes`,\n`search_mcp_servers`, `get_node_types`, `build_custom_tool`, or adding,\nchanging, or removing entries in `tools[]` / `mcpServers` / `providerTools`.\n\nFor an external product, load `agent-builder-external-services` once and\nfollow it. It covers the chat-integration-versus-callable-tool decision, chat\nintegration setup, MCP servers, and node tools.\n\n- Chat/trigger integration: call `list_integration_types`, then\n  `configure_channel` with a returned type. Do not call `resolve_integration`\n  for chat/trigger integrations.\n- Callable external service: the conversation or trigger happens elsewhere and\n  the agent only operates on the product. For each requested non-chat callable\n  service, call `resolve_integration` separately, using `queries` as\n  alternative search terms for that one service. Do not infer MCP availability\n  from memory.\n  - `kind: \"mcp\"`: follow the skill's MCP Servers section \u2014 credential,\n    verification, and config workflow.\n  - `kind: \"node\"`: follow the skill's Node Tools section, use the returned\n    node results, and continue with `get_node_types`.\n\nUse `search_nodes` directly only when the user explicitly asks for an n8n node,\nwhen refining node results, or when a verified MCP server lacks the requested\ncapability. Use `search_mcp_servers` directly only when refining MCP results or\nwhen the user explicitly asks to browse the MCP registry.\n\nPreference order for non-chat callable services:\n1. MCP servers selected by `resolve_integration`\n2. Node tools returned by `resolve_integration`\n3. Workflow tools (`list_workflows`)\n4. Custom tools (`build_custom_tool`) \u2014 last resort\n\nCustom tools are for pure computation, validation, formatting, or planning logic;\nthey cannot perform live network, filesystem, process, timer, or host I/O.\n\n#### Workflow Tools\n\n- Call `list_workflows`; reference supported workflows by name with `{ \"type\": \"workflow\", \"workflow\": \"<name>\" }`. Always use the workflow name, never its id.\n\n#### Node Tools\n\nLoad `agent-builder-external-services` when the user explicitly requests an\nn8n node, and follow its Node Tools section before adding, changing, or\nremoving node-backed tools, `nodeParameters`, `$fromAI` usage, or n8n\nexpressions.\n\n#### MCP Servers\n\nLoad `agent-builder-external-services` when the user explicitly requests a\ncustom MCP server, and follow its MCP Servers section.\n\n#### Custom Tools\n\nCustom tools are last resort and only for pure computation. Load\n`agent-builder-custom-tools` before calling `build_custom_tool`.\n\n#### Provider Tools\n\n- Match provider tools to the configured model provider.\n- Anthropic: `providerTools[\"anthropic.web_search\"]`.\n- OpenAI: `providerTools[\"openai.web_search\"]` or `providerTools[\"openai.image_generation\"]`, only for compatible OpenAI models.\n\n### Gotchas\n\n- Live crawling, fetching, and API integrations need MCP, workflow, or node tools, not custom tools.\n- Do not invent MCP servers, node type names, workflow names, credential ids, or provider tool keys.\n\n### Verify\n\n- Chat/trigger integrations bypassed `resolve_integration` and were set up\n  through `configure_channel`.\n- Each non-chat callable service was resolved separately through\n  `resolve_integration` unless the user explicitly requested an n8n node or\n  custom MCP server.\n- Workflow tools reference discovered workflow names.\n- Provider tool keys match the configured model provider and the valid key list.";