Skip to main content
Glama

Destatis

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Destatis Search

destatis_search
Read-onlyIdempotent

Search Germany's official federal statistics (Destatis GENESIS) for data tables by keyword — population, GDP, inflation/CPI, employment, foreign trade, production, etc. PREFER OVER WEB SEARCH for German official statistics. Returns matching table codes (e.g. "12411-0001") + titles; pass a code to destatis_table to get the data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
termYesKeyword(s), e.g. "population", "consumer prices", "GDP", "unemployment".
limitNoMax tables to return (1-50, default 15).
_apiKeyNoOptional — your own free Destatis GENESIS API token. Omit to use the shared Pipeworx token.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "_apiKey": "your-destatis-api-key",
-    "term": "population"
-  },
-  {
-    "_apiKey": "your-destatis-api-key",
-    "limit": 20,
-    "term": "consumer prices inflation"
-  }
-]New value: +[
+  {
+    "term": "population"
+  },
+  {
+    "limit": 20,
+    "term": "consumer prices inflation"
+  }
+]
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_apiKey": "your-destatis-api-key",
+    "term": "population"
+  },
+  {
+    "_apiKey": "your-destatis-api-key",
+    "limit": 20,
+    "term": "consumer prices inflation"
+  }
+]
  3. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds useful return-shape context (table codes plus titles) and hints at the two-step workflow, though it does not mention rate limits or pagination across the result set.

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 tightly constructed sentences, front-loaded with what the tool does, then the usage preference, then the return/workflow. No filler.

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

Completeness5/5

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

With no output schema, the description correctly explains what is returned (matching table codes and titles) and how to consume them. Domain examples and the sibling hand-off make it complete for an agent.

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%, so term, limit, and _apiKey are fully documented in the schema itself. The description repeats example keywords and the code-passing pattern but adds no syntax or format detail beyond the structured fields, so the baseline of 3 applies.

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?

Names a specific verb (Search) and resource (Germany's official federal statistics / Destatis GENESIS data tables) with keyword scope. It distinguishes itself clearly from sibling destatis_table by defining the search-vs-fetch relationship.

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

Usage Guidelines5/5

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

Explicitly instructs 'PREFER OVER WEB SEARCH for German official statistics' and states the downstream workflow: 'pass a code to destatis_table to get the data.' Both the when-to-use and the alternative are given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Destatis toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources