DatoQA

get_economic_indicators

Read-onlyIdempotent

Eurostat HICP annual inflation rate (monthly), seasonally adjusted unemployment rate (monthly), or real GDP growth over the previous quarter (quarterly). EU/EFTA only, since 2020 through latest published periods. Source flags, missing cells, units and evidence retained. Use list_economic_indicators for countries; not real-time or independently verified.

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": {
      "country": "<country>",
      "indicator": "<indicator>"
    },
    "name": "get_economic_indicators"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum latest monthly or quarterly observations returned, default 24.
`country`	Yes	Eurostat EU/EFTA country code from list_economic_indicators, for example FR or EL for Greece; not a World Bank three-character code.
`language`	No	Response metadata language: en or fr; original source notes are preserved.	en
`indicator`	Yes	Eurostat series key from list_economic_indicators; check frequency, units and adjustment.

Output Schema

Name	Required	Description	Default
`record`	No
`status`	Yes
`country`	Yes
`returned`	Yes
`directory`	No
`indicator`	Yes
`interpretation`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 28, 2026

changedInput schema / $schema

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

changedOutput schema / $schema

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

Changed1 schema field changedSep 27, 2026

changedOutput schema / properties / record / properties / provenance / properties / verification_level / enum

Previous value: -[
-  "official_source_and_schema_checked",
-  "method_specific"
-]New value: +[
+  "official_source_and_schema_checked",
+  "public_aggregator_and_schema_checked",
+  "method_specific"
+]

First observedSep 27, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description goes further with data-provenance behavior: source flags, missing cells, units and evidence are retained, and the data is explicitly 'not real-time or independently verified.' That last caveat is exactly the kind of trait an agent needs and cannot get from annotations.

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 densely packed sentences with no filler, and the series/scope information is front-loaded. It is terse but every clause carries information; the only cost is slight density that borders on note-form.

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?

With a 100%-covered schema, output schema present, and annotations carrying safety, the description's remaining obligations are scope and data-quality caveats — both delivered. It could be more complete by distinguishing from the sibling 'indicator' tools, but nothing required for a correct call is missing.

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 country codes (EL for Greece, not World Bank 3-char), enum values, language and limit are already documented in the schema. The description adds no parameter-level detail beyond what the schema provides, so baseline 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 three concrete series (HICP annual inflation, seasonally adjusted unemployment, real GDP growth), their frequencies, and the geographic scope (EU/EFTA, since 2020). An agent can distinguish this from get_us_economic_indicators and get_historical_indicators without opening a schema.

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 states when to route elsewhere ('Use list_economic_indicators for countries') and gives hard scope limits (EU/EFTA only, since 2020, not real-time). It does not, however, contrast with the closely-named get_indicators or get_historical_indicators siblings, leaving some ambiguity about which indicator tool to pick.

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?