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, and MCP servers. Load `agent-builder-node-tools` before\nconfiguring a node tool.\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- A configured chat integration generates its own context and action tools for\n  every top-level Agent run, including scheduled tasks. When its capabilities\n  include the requested action, do not add a same-platform node, MCP, or\n  workflow tool. A scheduled or proactive message with no inbound conversation\n  is not, by itself, a reason to add another tool.\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\"`: load `agent-builder-node-tools`, use the returned node\n    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 with `{ \"type\": \"workflow\", \"workflowId\": \"<id>\", \"workflow\": \"<name>\" }` using both values it returns.\n\n#### Node Tools\n\nLoad `agent-builder-node-tools` before adding, changing, or removing\nnode-backed tools, `nodeParameters`, `$fromAI` usage, or n8n expressions.\nFor an HTTP Request Tool, use only an exact URL explicitly supplied by the\nuser. If the user has not supplied one during an initial build, you MUST ask\nfor it through the trailing `finish_setup` call, then configure the tool with\nthe answer. On later turns, use `ask_questions` before mutating the config.\nNever infer or invent a URL.\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- Generic web search must use `config.webSearch`; never add an HTTP Request\n  Tool unless the user explicitly requests direct HTTP, API, or specific-page\n  fetching.\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- Do not duplicate an action already supplied by a configured chat integration.\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 IDs and names.\n- Provider tool keys match the configured model provider and the valid key list.";