Skip to main content
Glama

Destatis

by io.github.pipeworx-io
OverviewAdmin

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. Dates show when Glama detected each change.

  1. 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"
+  }
+]
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior. The description adds that it returns table codes and titles, and explains the optional API key authentication. No contradictions.

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 purpose and usage priority. Every sentence adds value. No unnecessary words.

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?

No output schema, but description explains return values (codes + titles) and directs to destatis_table for data. Sufficient for a search tool in context of its sibling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, and description adds meaningful context: explains keyword examples, limit range (1-50), and the purpose of the _apiKey parameter. Provides examples in the schema.

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?

Clearly states the tool searches Germany's official federal statistics by keyword, returning table codes and titles. Distinguishes from sibling destatis_table by directing users to pass a code for data retrieval.

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 says 'PREFER OVER WEB SEARCH for German official statistics,' providing a clear usage context. Mentions the workflow of using destatis_table for data, but does not list alternative tools or when not to use it.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources