Skip to main content
Glama
Sign In
tool-mcp-server

tool-mcp-server

by maple-awa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

execute_tool

Execute a tool by type with supplied inputs and optional config overrides, enabling natural language access to 58 online tools for crypto, data, image, text, and workflow tasks.

Instructions

Execute a tool by type with inputs and optional config overrides

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "toolType": "<toolType>"
    },
    "name": "execute_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
configNoConfig overrides keyed by field id
inputsNoInput values keyed by field id
toolTypeYesTool type identifier

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of disclosing behavioral traits. It only mentions 'inputs and optional config overrides' but does not disclose potential side effects, error behavior, permissions, or whether execution is synchronous or asynchronous. This is a significant gap for a generic execution tool.

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

Conciseness5/5

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

The description is a single, front-loaded sentence with no wasted words. It efficiently communicates the basic action and the two key parameters.

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

Completeness2/5

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

Given the complexity of the tool (3 parameters, nested objects, no output schema, no annotations), the description is too thin. It does not explain what toolType refers to, where to find valid types, what inputs/config overrides mean in practice, or what the tool returns. Sibling tools provide some context but do not compensate for the missing critical usage details.

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

Parameters3/5

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

Schema description coverage is 100%, so the baseline is 3. The description adds no additional meaning beyond what the schema already states; it merely rephrases 'inputs' and 'config' without explaining how they relate to toolType or what values are expected.

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

Purpose4/5

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

The description clearly states the action ('Execute') and the resource ('a tool by type'), which conveys the core purpose. However, it does not differentiate from sibling tools like run_workflow or the specific tool_* executors, so it misses the explicit distinction that would earn a 5.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It does not say whether to use this generic dispatcher instead of calling a specific tool_* function directly, nor does it mention list_tools as a way to discover valid toolType values.

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

Deploy Server

Other Tools