Skip to main content
Glama

Invoke any Swissyphus tool by name

call_tool
Read-only

Invoke any exposed Swiss public data tool by name using a discovery preset, keeping context small while validating arguments against its schema and returning the tool's exact output.

Instructions

Invoke any Swissyphus tool this server exposes by name, with the 'discovery' preset that includes every module, so the context stays small while the full catalogue is reachable. Arguments are validated against the tool's schema (see describe_tool). Returns exactly what the tool returns.

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": {
      "name": "<name>"
    },
    "name": "call_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesTool name from find_tools / find_data
argumentsNoArguments object for that tool

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A4.2/5.0
Behavior3/5

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

Beyond readOnlyHint/openWorldHint it discloses two real traits: arguments are validated against the target tool's schema, and the return value is a pure passthrough ('exactly what the tool returns'), which matters because there is no output schema. It does not state what happens on an invalid or unknown tool name, nor that effects/side effects of the invoked tool propagate, which is the main behavioral question for a dispatcher.

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?

Two sentences, front-loaded with the action and the preset constraint, then the validation and return semantics. No filler, and the parenthetical '(see describe_tool)' earns its place by routing the agent.

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

Completeness4/5

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

For a two-parameter passthrough tool with a nested free-form arguments object, the definition covers how to name the tool, how arguments are validated, and what comes back even though no output schema exists. The remaining gap is failure behavior for bad names or rejected arguments, which is relevant for a dispatcher.

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%, so the baseline would be 3; the description adds meaning by saying argument validation is delegated to the target tool's schema and pointing at describe_tool for that schema, and the name parameter is sourced from find_tools/find_data. That is genuine guidance on how to construct the nested 'arguments' object rather than a restatement.

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?

Specific verb plus resource: 'Invoke any Swissyphus tool this server exposes by name'. This is unmistakably a generic dispatcher, distinct from find_tools/describe_tool which locate or describe tools, and the agent can tell that apart without opening the schema.

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

Usage Guidelines4/5

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

It gives a clear rationale for choosing this route: the 'discovery' preset keeps the context small while the full catalogue stays reachable, so the agent knows to use call_tool to reach tools not already loaded. It stops short of explicit exclusions (e.g. when to prefer directly-invoked tools or find_tools first), so it is clear context rather than full when/when-not guidance.

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