Skip to main content
Glama

UK Data for Agents

eu_youth_unemployment_rate

Read-onlyIdempotent

Monthly unemployment rate for people under 25 (seasonally adjusted, % of the under-25 labour force) in one European country. Answers "how high is youth unemployment in Spain or Greece". Source: Eurostat dataset une_rt_m. Some countries publish youth figures only quarterly or with a lag, so recent months may be null; ask for 4 or more months. (cost: 1 credit)

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": "eu_youth_unemployment_rate"
  }
}

Input Schema

NameRequiredDescriptionDefault
nNointeger, optional, most recent months, 1-100, default 12
geoNostring, required, 2-letter Eurostat country code (DE, FR, ES, IT, NL, PL, EL = Greece) or country name; EU27_2020, EA (euro area), EA21, EA20 also accepted. EU, EFTA and EU candidate countries only (no UK)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds real context beyond that: seasonality adjustment, the Eurostat dataset of origin, the fact that some countries publish youth figures quarterly or with a lag so recent months may be null, and the 1-credit cost. That is exactly the kind of operational trait annotations cannot express.

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?

Front-loaded with the core definition, then source, then the data-lag caveat, then cost. Dense with parentheticals but each sentence carries distinct information; nothing is padding.

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?

For a two-parameter read-only time series with no output schema, the description conveys the measure, unit, adjustment, source and the main data-quality pitfall. Only the exact return shape (monthly series length, field names) is unstated, which is minor for such a simple 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 coverage is 100%, with the geo codes, EU27/EA aggregates and the n range already fully documented in the schema, so baseline 3 applies. The description adds only a light recommendation on n ('ask for 4 or more months') and the 'one European country' scoping, which is useful but marginal against the schema's own detail.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific resource and unit: 'Monthly unemployment rate for people under 25 (seasonally adjusted, % of the under-25 labour force) in one European country', plus the source dataset une_rt_m. The age restriction distinguishes it implicitly from the sibling eu_unemployment_rate, but that sibling is never named, so the agent must infer the split.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It provides an example question ('how high is youth unemployment in Spain or Greece') and a practical instruction to 'ask for 4 or more months' because recent data may be null. However, there is no explicit when-not guidance or routing to eu_unemployment_rate for the all-ages rate, so the sibling choice is left implicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources