Skip to main content
Glama

search_statistics

Read-onlyIdempotent

Search BFS datasets on opendata.swiss by query and set an optional limit to find relevant Swiss statistics.

Instructions

Search BFS datasets on opendata.swiss

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": "search_statistics"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo1–20
queryYese.g. unemployment, GDP

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.9.0
    • addedInput schema / properties / limit / default
      Added value: +10
    • changedInput schema / properties / limit / description
      Previous value: -"Max results to return (1–20, default 10)"New value: +"1–20"
    • changedInput schema / properties / query / description
      Previous value: -"Search query (e.g. 'unemployment', 'GDP', 'housing prices', 'birth rate')"New value: +"e.g. unemployment, GDP"
  2. First observed

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered structurally. The description adds nothing beyond that: no indication of what a match means, whether results are ranked, whether an empty query is allowed, or what identifiers come back for follow-up calls.

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

Conciseness4/5

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

A single short sentence with no filler, front-loaded with the verb and resource. It is efficient but borders on under-specified rather than genuinely tight.

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?

The tool is simple (2 params, no output schema), but the description never says what the results are or how to use them — critical here because siblings get_opendata_dataset and list_opendata_resources likely consume IDs returned by this search. Combined with no sibling routing, the definition leaves too much to inference.

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%, with query examples ("unemployment, GDP") and the limit range (1–20) documented inline. The description contributes no additional parameter meaning, so the baseline of 3 applies.

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

Purpose3/5

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

The description gives a verb ("Search") and a resource ("BFS datasets on opendata.swiss"), so the general intent is graspable. However, the tool name says "statistics" while the description says "datasets", and the sibling set contains search_opendata, get_statistic and get_opendata_dataset, so an agent cannot tell from this sentence how the scope actually differs from those.

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?

There is no when-to-use guidance, no exclusion, and no mention of the closely related siblings (search_opendata, get_statistic, get_opendata_dataset). The agent must guess which of the several search/statistics tools is appropriate.

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