Skip to main content
Glama

EU Annual GDP Growth

finance.eurostat.gdp_growth
Read-onlyIdempotent

Retrieve annual real GDP growth rate (chain-linked volumes, % change vs previous year) for any EU country or aggregate using Eurostat data. Specify country, start and end period.

Instructions

Annual real GDP growth rate (chain-linked volumes, % change vs previous year) for one EU country. Eurostat dataset tec00115, CC BY 4.0

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countryNoEurostat geo code — 2-letter country (DE, FR, IT, ES, UK, PL, ...) or aggregate ("EU27_2020", "EA20"). One country per call. Default: "EU27_2020".
sinceNoEarliest period to return — format depends on series frequency: "2020" (annual), "2024-01" (monthly), "2024Q1" (quarterly).
untilNoLatest period to return — same format as `since`.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultNoTool response payload. Shape varies per tool — consult the tool description and inputSchema. May be an object, array, string, or number depending on the upstream provider response.
errorNoPresent only when the call failed. Includes error code, message, request_id, and any provider-specific extras.
Behavior4/5

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

Annotations already indicate readOnly, idempotent, and open world. Description adds dataset source (tec00115) and license (CC BY 4.0), plus clarifies the metric is chain-linked volumes. 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, no fluff. Each word adds value: specifies metric, data source, license, and scope ('for one EU country').

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?

Output schema is present, so return format is covered. Description identifies the data source and metric. Missing usage context (when to choose this over sibling tools) but otherwise complete for a read-only data tool.

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 covers 100% of parameters with descriptions. The tool description does not add extra meaning beyond the schema; it only restates the metric type. Baseline of 3 is appropriate.

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?

Description clearly states the tool provides 'Annual real GDP growth rate' for one EU country, referencing the exact dataset and license. It distinguishes from sibling tools like inflation, population, and unemployment by specifying GDP growth.

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 explicit guidance on when to use this tool vs other Eurostat tools (e.g., inflation, population). The description implies it's for GDP growth per country, but no exclusions or alternatives are mentioned.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/whiteknightonhorse/APIbase'

If you have feedback or need assistance with the MCP directory API, please join our Discord server