Luxembourg MCP

search_statistics

Search Luxembourg statistical dataflows by topic or title to find relevant datasets and indicators from STATEC and LUSTAT.

Instructions

Search STATEC LUSTAT statistical dataflows by topic or title.

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

Name	Required	Description	Default
`limit`	No
`query`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Jul 11, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations, the description should disclose behavioral traits. It only indicates the search action and criteria but fails to mention pagination, result limits, error handling, or any side effects. The read-only nature is not explicitly stated.

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?

The description is a single, concise sentence that front-loads the core purpose. No extraneous words, ideal for quick parsing by an AI agent.

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?

Given the tool is a search with no output schema, the description lacks details on return values, result format, or behavior with empty results. It is incomplete for an agent to understand what to expect.

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

Parameters2/5

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

Schema coverage is 0%, so the description must compensate. It mentions 'by topic or title' which hints at the query parameter's use, but does not explicitly describe `query` or `limit`. The `limit` parameter is not addressed at all, leaving the agent to infer its purpose from 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?

The description clearly states the verb 'Search', the specific resource 'STATEC LUSTAT statistical dataflows', and the search criteria 'by topic or title'. It effectively distinguishes this tool from sibling tools that search other domains (e.g., datasets, legislation).

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?

No guidance is provided on when to use this tool versus alternatives like search_datasets or search_legislation. The description does not mention when not to use it or any prerequisites.

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