Skip to main content
Glama

get_statistic

Read-onlyIdempotent

Retrieve details and resource links for a Swiss BFS dataset using its opendata.swiss ID, typically obtained from statistical search results.

Instructions

Details and resource links for a BFS dataset by opendata.swiss ID (from search_statistics)

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

Input Schema

NameRequiredDescriptionDefault
dataset_idYese.g. bevolkerungsstatistik-einwohner

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.9.0
    • changedInput schema / properties / dataset_id / description
      Previous value: -"Dataset identifier from opendata.swiss (e.g. 'bevolkerungsstatistik-einwohner')"New value: +"e.g. bevolkerungsstatistik-einwohner"
  2. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive behavior. The description adds that the response includes details and resource links, which is useful because there is no output schema, but it does not cover error behavior or permissions.

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?

One compact sentence, front-loaded with the return content and identifier source; no redundant wording.

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 simple one-parameter lookup with full schema coverage and annotations, the description covers what the tool returns and where the ID comes from. It could say more about the detail fields, but no output schema exists and the core need is met.

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% and the single parameter has an example. The description adds that the ID is an opendata.swiss ID obtained from search_statistics, which is meaningful context beyond the schema.

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?

States it returns details and resource links for a BFS dataset identified by opendata.swiss ID, and ties the ID to search_statistics. This distinguishes it from the search tool, though it does not explicitly contrast with get_opendata_dataset.

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

Usage Guidelines3/5

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

Implies it should be used after search_statistics to fetch a specific dataset, but gives no explicit when-not guidance or alternatives such as get_opendata_dataset.

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