euroref — European government reference data

get_country_brief

Read-onlyIdempotent

PAID ($0.01). Country brief: every reference series we hold for one country (policy rate, VAT/GST, CPI, taxes, minimum wage, holidays...) in one call, each with value, unit, effective and last-confirmed dates, official source and confidence label. Cheaper than buying the series one by one. Pass api_key if you have one (card checkout at /pricing); otherwise the response explains how to pay via x402. After a 200, bind get_changes (free poll) or register_alert (HMAC push; Register: $0 · Delivery after trial: $0.05) on this series so a later gazette does not silently retire the value.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`api_key`	No	API key
`country`	Yes	ISO country code

Output Schema

TableJSON Schema

Name	Required	Description
`name`	No
`as_of`	No
`error`	No	Present on a free refusal or error; no charge
`series`	No
`country`	No
`no_charge`	No
`price_usd`	No
`disclaimer`	No
`how_to_pay`	No
`bind_series`	No
`explanation`	No
`x_next_bind`	No
`series_count`	No
`http_endpoint`	No
`payment_required`	No	true when the call needs payment; how_to_pay explains x402 or card

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 17, 2026
- removedOutput schema / properties / series / items / properties / label_basis / properties / source_type / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / series / items / properties / label_basis / properties / source_type / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / series / items / properties / label_basis / properties / verification_age_days / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / series / items / properties / label_basis / properties / verification_age_days / type
```
Added value: +[
+  "number",
+  "null"
+]
```
AddedOct 17, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive, openWorld), but the description goes further: it discloses the $0.01 cost, the payment fallback behavior, the shape of each returned series (value, unit, effective/last-confirmed dates, source, confidence), and the risk of values being silently retired without an alert.

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?

Dense but front-loaded: purpose and price come first, then payment, then follow-up. Nearly every sentence carries unique information, though the long parenthetical list of series types and the pricing aside make it slightly heavier than needed.

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?

Covers purpose, cost, auth path, return contents, and downstream sibling routing; with an output schema present it is more than complete for an agent to call this correctly.

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?

Schema coverage is 100% so both parameters are already documented. The description still adds value by clarifying api_key is optional and what happens without it (x402 payment instructions), which is not in the schema's terse 'API key' text.

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 resource (a bundled country brief of every reference series held for one country) and enumerates what it includes, so an agent can instantly distinguish it from get_series/list_series which fetch individual series.

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 says it is cheaper than buying series one by one, explains the api_key vs x402 payment paths, and prescribes follow-up actions (bind get_changes or register_alert) after a 200. Clear when-to-use and what-to-do-next guidance.

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

All euroref — European government reference data 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?