Skip to main content
Glama

Find the right Swissyphus tool

find_tools
Read-only

Search all Swiss public data tools by keyword to discover names, purposes, and load status; use describe_tool for schema and call_tool to invoke unloaded tools.

Instructions

Keyword search over all Swissyphus tools this server exposes (with the 'discovery' preset: every module, loaded or not). Returns tool names, what they do, and whether they are loaded. Use describe_tool for the argument schema and call_tool to invoke a tool that is not loaded. Example: 'avalanche danger', 'company VAT', 'train delays', 'court decision'.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesWhat you want to do

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds genuine value by disclosing the result shape (names, what they do, loaded status) and that the search spans unloaded modules via the discovery preset. It says nothing about result caps or how many matches come back, which matters given a maximum limit of 30.

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?

Three short sentences, front-loaded with what it searches and what it returns, followed by routing guidance and then examples. The parenthetical about the discovery preset carries real information rather than padding, and no sentence is redundant.

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 only two parameters and no output schema, the description does the right things: it explains the return fields and the search scope. Remaining gaps are the undocumented limit parameter and the absence of any note on how results are ranked or truncated, which an agent sizing its query would want.

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 coverage is only 50%: query has a terse description and limit has none. The description compensates for query by giving four concrete example keywords ('avalanche danger', 'company VAT', 'train delays', 'court decision') that show the expected phrase granularity, but it never mentions limit, its default, or its cap, leaving half the parameters undocumented in prose.

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?

States a specific verb and resource ('Keyword search over all Swissyphus tools'), scopes it precisely ('with the discovery preset: every module, loaded or not'), and implicitly separates it from the invocation path by naming call_tool. An agent can tell this is the discovery entry point without opening a 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?

Explicitly routes the agent: describe_tool for argument schemas, call_tool to invoke a tool that is not loaded. That covers the two natural alternatives. It stops short of saying when find_tools itself is unnecessary (e.g. when the target tool is already loaded and known), 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