Invoke a tool by name. input is forwarded raw to the tool handler.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Exact tool name to invoke (e.g. "accounting-invoices-create"), as returned by list_tools. | |
| input | No | Arguments object forwarded verbatim to the target tool. Its shape matches that tool's input schema (fetch it with describe_tool_input). Omit for tools that take no arguments. |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Input schema / $schemaRemoved value: -"http://json-schema.org/draft-07/schema#"Input schema / properties / input / additionalPropertiesAdded value: +{}Input schema / properties / input / descriptionAdded value: +"Arguments object forwarded verbatim to the target tool. Its shape matches that tool's input schema (fetch it with describe_tool_input). Omit for tools that take no arguments."Input schema / properties / input / propertyNamesAdded value: +{
+ "type": "string"
+}Input schema / properties / input / typeAdded value: +"object"Input schema / properties / name / descriptionAdded value: +"Exact tool name to invoke (e.g. \"accounting-invoices-create\"), as returned by list_tools."Input schema / requiredPrevious value: -[
- "name",
- "input"
-]New value: +[
+ "name"
+]Input schema / properties / argumentsRemoved value: -{
- "additionalProperties": {},
- "description": "Arguments for the target tool as a JSON object, matching the schema returned by describe_tool_input.",
- "properties": {},
- "type": "object"
-}Input schema / properties / inputAdded value: +{}Input schema / properties / name / descriptionRemoved value: -"The name of the tool to execute"Input schema / requiredPrevious value: -[
- "name"
-]New value: +[
+ "name",
+ "input"
+]Input schema / properties / argumentsAdded value: +{
+ "additionalProperties": {},
+ "description": "Arguments for the target tool as a JSON object, matching the schema returned by describe_tool_input.",
+ "properties": {},
+ "type": "object"
+}Input schema / properties / inputRemoved value: -{
- "additionalProperties": {},
- "description": "Input parameters for the tool as a JSON object",
- "propertyNames": {
- "type": "string"
- },
- "type": "object"
-}Input schema / properties / nameAdded value: +{
+ "description": "The name of the tool to execute",
+ "type": "string"
+}Input schema / properties / tool_nameRemoved value: -{
- "description": "The name of the tool to execute",
- "type": "string"
-}Input schema / requiredPrevious value: -[
- "tool_name"
-]New value: +[
+ "name"
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses that input is 'forwarded raw,' which is a behavioral detail beyond what annotations alone convey (e.g., openWorldHint, readOnlyHint). This tells agents that arguments are not preprocessed, which is essential for constructing valid input. No contradictions with annotations exist.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences, front-loaded with the core purpose and free of redundant information. Every word earns its place, and the structure is clean and scannable.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is a dynamic dispatcher with rich schema descriptions and annotations covering side-effect hints, so the description is largely sufficient. It does not describe the return value or error behavior, but those are inherently dependent on the invoked tool and less critical given the schema's thoroughness. A slightly more explicit note about behavior varying by target tool would improve it.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% as both parameters have detailed descriptions, so the baseline is 3. The description adds little beyond the schema, as 'forwarded raw' essentially repeats the schema's 'forwarded verbatim' for the input parameter. No additional parameter semantics are provided.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's function with a specific verb and resource: 'Invoke a tool by name.' This distinguishes it from sibling tools like list_tools or describe_tool_input, which inspect rather than execute. The additional phrase about forwarding input raw further clarifies the tool's role.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
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 mention prerequisites, such as looking up the tool name with list_tools or fetching the input schema with describe_tool_input. Those details appear only in the schema property descriptions, not in the main description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool serves a distinct purpose: discovering tools, describing inputs, executing tools, and listing scopes. There is no overlap or ambiguity.
All tools follow a consistent verb_noun pattern in snake_case (list_tools, describe_tool_input, execute_tool, list_scopes), making them predictable.
With 4 tools covering discovery, description, execution, and permission scoping, the set is concise and appropriate for a meta-tool server, though slightly minimal.
The tool surface fully covers the required operations for managing and using tools: listing, describing, executing, and checking scopes, with no obvious gaps.