export declare const toolSelectionTemplate = "\n{{{mcpProvider.text}}}\n\n{{{recentMessages}}}\n\n# Tool Selection Instructions\n\nYou are selecting the appropriate biological research tool to address a user's request from the MCP servers listed above.\n\n## CRITICAL SERVER NAME REQUIREMENTS:\n1. **EXACT MATCH REQUIRED**: The \"serverName\" in your response MUST match EXACTLY the server name shown in [SERVER NAME] above\n2. **CASE SENSITIVE**: Server names are case-sensitive - \"biostratum-gget\" \u2260 \"biostratum-Gget\" \u2260 \"gget\"\n3. **NO ABBREVIATIONS**: Use the complete server name as shown (e.g., \"biostratum-gget\", NOT \"gget\")\n4. **NO MODIFICATIONS**: Don't add or remove prefixes, suffixes, or change formatting\n\n## CRITICAL TOOL NAME REQUIREMENTS:\n1. **EXACT MATCH REQUIRED**: The \"toolName\" must match EXACTLY the tool name shown in the tools list\n2. **CASE SENSITIVE**: Tool names are case-sensitive and format-sensitive\n3. **NO MODIFICATIONS**: Copy the exact tool name including underscores, dashes, and capitalization\n\n## Selection Process:\n1. Analyze the user's request to understand their core information need or task\n2. Find the most appropriate tool based on its capabilities and the user's request\n3. Extract ACTUAL VALUES from the conversation context for tool arguments (no placeholders!)\n4. If no tool seems appropriate for the request, output {\"noToolAvailable\": true}\n\n## Response Format:\n- Your response MUST be valid JSON only (no code blocks, no comments, no explanatory text)\n- Use this exact structure:\n\n{\n  \"serverName\": \"exact-server-name-from-list-above\",\n  \"toolName\": \"exact-tool-name-from-list-above\", \n  \"arguments\": {\n    \"param1\": \"actual-value-from-conversation\",\n    \"param2\": \"actual-value-from-conversation\"\n  },\n  \"reasoning\": \"Brief explanation of why this tool matches the user's request\"\n}\n\n## Argument Requirements:\n- Extract REAL VALUES from the conversation context\n- NO placeholder values like \"example\", \"your-value\", \"replace-with\", etc.\n- Use proper JSON types: strings in quotes, numbers without quotes, booleans as true/false\n- ALWAYS use \"arguments\" as the key (NOT \"parameters\")\n\n## Invalid Examples to AVOID:\n\u274C \"serverName\": \"gget\" (should be \"biostratum-gget\")\n\u274C \"serverName\": \"Biostratum-gget\" (wrong capitalization)\n\u274C \"toolName\": \"Get_Info\" (wrong capitalization for gget_info)\n\u274C \"arguments\": {\"gene\": \"your-gene-here\"} (placeholder value)\n\u274C Adding code blocks or explanatory text outside JSON\n\n## Valid Example:\n\u2705 {\n  \"serverName\": \"biostratum-gget\",\n  \"toolName\": \"gget_search\",\n  \"arguments\": {\n    \"search_terms\": [\"FOXO3\"],\n    \"species\": \"homo_sapiens\",\n    \"limit\": 1\n  },\n  \"reasoning\": \"User wants to search for FOXO3 gene information, this tool provides gene search capabilities\"\n}\n\nREMEMBER: Your response will be parsed as JSON. Any deviation from pure JSON format will cause parsing failure!\n";