DatoQA

list_economic_indicators

Read-onlyIdempotent

Eurostat EU/EFTA country codes and monthly/quarterly economic series since 2020. Includes latest published periods, source definitions, units and collection status. Country codes differ from World Bank; Greece is EL.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_economic_indicators"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`period`	Yes
`source`	Yes
`endpoint`	Yes
`countries`	Yes
`collection`	Yes
`indicators`	Yes
`country_code_system`	Yes
`independently_verified`	Yes	Official-source checks are not independent factual corroboration.
`refresh_interval_seconds`	Yes
`max_collection_age_seconds`	Yes
`configured_country_allowlist`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 28, 2026

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

First observedSep 27, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description usefully adds content-level behavior (latest published periods, source definitions, units, collection status, 2020 start), which is genuine context beyond the annotations, though it omits ordering, pagination and update cadence.

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?

Three dense sentences with the scope front-loaded in the first and a practical caveat last; no filler. Slightly compressed but every clause carries information.

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

Completeness3/5

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

An output schema exists, so return-value explanation is not required. However, for a no-param catalog tool the description should state its role relative to the get_* siblings and any ordering/update behavior; that routing information is missing.

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?

The tool takes zero parameters, so the baseline is 4. The note that 'Country codes differ from World Bank; Greece is EL' adds real semantic value for downstream calls that must supply codes.

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 names the source (Eurostat), scope (EU/EFTA), frequency (monthly/quarterly) and coverage window (since 2020), but never states plainly that this is a catalog/list of available series and country codes, leaving the 'list' verb under-specified. It also does not distinguish itself from close siblings like get_economic_indicators, get_indicators, or list_historical_indicators.

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 when-to-use guidance is given. With siblings such as get_economic_indicators, get_indicators and list_historical_indicators, the agent has no signal for choosing this listing tool over the data-fetching ones.

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

All DatoQA tools Inspect

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

Need Help?