Agent Data Hub

Get a full time series

get_series

Read-onlyIdempotent

Returns complete numeric histories as compact CSV (t,value) from this service's archive of openly licensed series, e.g. ECB FX rates since 1999 (fx.EUR.USD), World Bank indicators for all countries since 1960 (wb.FP.CPI.TOTL.ZG.DE), ECB rates and 10y yields (ecb.rate.deposit, ecb.yield10y.IT), Eurostat, Statistics Canada, ONS and FAO series, German power prices (smard.price.day), sunspots since 1749 (noaa.sunspot-number). Pass q to search series ids, or id to fetch one (max 1,000 points, most recent kept). When to use: for many periods of one number (e.g. yearly inflation since 2000, monthly FX since 2010), with from/to and resample. For the latest value with context use ask_anything; get_history only holds values this service recorded from live endpoints. Read-only, no API key or signup. Free quota: 1000 calls/day per IP, shared across tools.

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

Input Schema

Name	Required	Description
`q`	No	Search series by keywords, e.g. "inflation germany" (returns ids, no data)
`id`	No	Series id to fetch, e.g. fx.EUR.USD
`to`	No	End, inclusive: year (2025 = through Dec 31), month or date
`agg`	No	Aggregation for resample (default mean)
`from`	No	Start: year (2010), month (2010-06) or date
`resample`	No	Aggregate to day/week/month/quarter/year

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 28, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), and the description goes well beyond them: discloses CSV (t,value) return shape, the 1,000-point cap with most-recent-kept truncation semantics, the 1000 calls/day per-IP quota shared across tools, and that no API key or signup is needed. Truncation and quota behavior are non-obvious and materially affect how an agent should call it.

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-loads purpose and return format, then examples, then routing guidance, then limits — a sensible order. The long enumerated example list is somewhat dense but earns its place by teaching id syntax that is otherwise hard to guess.

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?

For a read-only, schema-complete, annotation-covered tool with no output schema, the description supplies everything an agent needs: return format, truncation cap, quota, auth requirements, and routing to siblings. No material gap remains.

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% including two enums, so the schema already carries the meaning of q, id, from, to, resample and agg. The description adds only lightly, mostly restating the q-vs-id split and noting from/to with resample as a workflow. Baseline 3 is appropriate where the schema does the heavy lifting.

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?

States a specific verb and resource (returns complete numeric time-series histories as CSV t,value) and immediately scopes it with the archive it draws from. Rich concrete examples of series ids (fx.EUR.USD, wb.FP.CPI.TOTL.ZG.DE, noaa.sunspot-number) make the resource unambiguous and clearly separate it from ask_anything and get_history.

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?

Explicit 'When to use' section names the condition (many periods of one number, e.g. yearly inflation since 2000) and names the alternatives with their distinct roles: ask_anything for the latest value with context, get_history for values recorded from live endpoints. It also distinguishes q (search, returns ids only) from id (fetch data).

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

All Agent Data Hub 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?