Skip to main content
Glama

What can Swissyphus do?

about_swissyphus
Read-only

Lists active Swiss data modules, their coverage, and example questions so agents can choose the right tool when unsure which fits a query.

Instructions

Orientation for agents: lists the active modules, what each covers, and example questions each can answer. Call this first if unsure which tool fits a Swiss data question.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "about_swissyphus"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds what the agent actually gets back (active modules, what each covers, example questions), which is essential behavioral information not in the annotations. It does not mention cost, latency, or the size/shape of the listing, but for a zero-parameter orientation tool this goes beyond the minimum.

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 agent-directed purpose and followed by the call condition; every clause carries information and there is no filler.

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?

With no parameters and no output schema, the description carries the burden of describing the return value, and it does so in outline (modules, coverage, example questions). A slightly richer sense of the response structure or how it relates to find_tools would make it complete.

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?

The tool takes no parameters, so the schema is trivially complete and the baseline of 4 applies. Nothing in the description is needed to explain arguments.

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 states a specific role — orientation that lists active modules, their coverage, and example questions — which is materially clearer than the title. It does not, however, distinguish itself from discovery-oriented siblings such as find_tools or describe_tool, so an agent cannot tell from this text alone which discovery entry point to pick.

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?

"Call this first if unsure which tool fits a Swiss data question" gives an explicit trigger condition and implicitly tells the agent to skip it when it already knows the right tool. It stops short of naming alternatives or stating when-not to call, so it is clear context without full routing 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