Skip to main content
Glama
SpiritHerb

MCP Research Router

by SpiritHerb

execute_tools

Execute tools from remote MCP servers individually or in batch parallel mode to speed up multi-tool workflows. Use when tools have no dependencies.

Instructions

执行从远程MCP服务器获取的工具(支持单个或批量并行执行)。

重要约束:

  • 此工具只能执行从远程MCP服务器获取的工具,工具名称格式为"server_name-tool_name"

  • 不能执行用户直接添加到MCP客户端的其他工具

  • 如果工具名称不是"server_name-tool_name"格式,说明该工具应该直接调用,不要通过此工具执行

如何区分:

  • 工具名称包含 "-" 且格式为 "server_name-tool_name" 则通过此工具执行

  • 工具名称不包含 "-" 或不是 "server_name-tool_name" 格式则直接调用

使用方式: 方式1:执行单个工具 {"tool_name": "server_name-tool_name", "arguments": {"参数名": "参数值"}} 方式2:批量并行执行多个工具(推荐,3-5倍速度提升){"tools": [{"tool_name": "server_name-tool_name", "arguments": {...}}, {"tool_name": "server_name-tool_name", "arguments": {...}}]}

性能优势: 当需要执行多个工具时,使用批量模式可以并行执行,提供3-5倍速度提升。所有工具同时执行,无需等待。

适用场景:

  • 单个工具执行:使用方式1

  • 多个工具(无依赖):使用方式2批量并行执行

  • 多个工具(有依赖):使用方式1顺序执行

注意事项:

  • 只能执行格式为 "server_name-tool_name" 的工具

  • 批量执行时,所有工具并行执行,互不等待

  • 如果工具之间有依赖关系,请使用方式1逐个执行

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tool_nameNo单个工具的名称,格式为"server_name-tool_name"(与tools参数二选一)
argumentsNo传递给单个工具的参数
toolsNo批量执行的工具数组(与tool_name参数二选一)
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations exist, so description carries full burden. It discloses key behaviors: only for remote tools, batch is parallel with 3-5x speedup, sequential for dependent tools. Does not cover error handling or synchronization details, but sufficiently explains core traits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-organized with headers, bullet points, and clear sections. It is thorough but each sentence contributes useful information. A slight reduction due to length, but efficient for the content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite no output schema, the description provides complete context: purpose, constraints, usage methods, performance benefits, and scenario recommendations. It distinguishes from the sibling and covers critical usage aspects comprehensively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and descriptions are already good. The description adds value by explaining the naming format 'server_name-tool_name' and clarifying mutual exclusivity between 'tool_name' and 'tools' parameters, beyond what schema states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Execute tools obtained from remote MCP servers' with a specific verb and resource. It distinguishes from sibling tool 'get_tool_list' by focusing on execution rather than listing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit guidance on when to use this tool vs. direct invocation, based on the naming convention 'server_name-tool_name'. Also details usage modes for single, batch parallel, or sequential execution with clear applicability to dependency scenarios.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SpiritHerb/mcp-research-router'

If you have feedback or need assistance with the MCP directory API, please join our Discord server