Skip to main content
Glama

Dbnomics Get Series

dbnomics_get_series
Read-onlyIdempotent

Fetch a specific time series. Series identified by (provider, dataset, series_code). Include observations to get the actual data points.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "dataset": "EXR",
      "provider": "ECB",
      "series_code": "EUR.USD.SP00.A"
    },
    "name": "dbnomics_get_series"
  }
}

Input Schema

NameRequiredDescriptionDefault
datasetYesDataset code
providerYesProvider code
series_codeYesSeries code (dot-separated dimensions or named code)
observationsNoInclude data points (default true)

Output Schema

NameRequiredDescriptionDefault
seriesNoSeries data with metadata

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds one genuine behavioral fact beyond that — that observations toggles whether actual data points come back, implying a metadata-only response otherwise — but says nothing about failure behavior for bad provider/dataset/series combinations or about response size.

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?

Two short sentences with no filler, and the core identification requirement is front-loaded immediately after the verb. Nothing is wasted, though the second sentence slightly overlaps the schema's own parameter descriptions.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With a full output schema and rich annotations, the description needn't explain return values or safety. What is missing is the navigation piece — how to obtain a series_code when you don't already have one — which matters given the presence of find_series and dbnomics_search as siblings.

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%, with each of the four parameters documented and two worked examples supplied, so the schema carries the burden. The description only restates the identifier triple and the observations flag, adding no new format or syntax detail beyond what the schema already provides.

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?

"Fetch a specific time series" names a concrete verb and resource, and the second sentence states the exact identifying triple (provider, dataset, series_code). It stops short of differentiating this from the sibling find_series, so an agent must infer that this is the direct-fetch path rather than the lookup path.

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?

Usage is only implied: by stating the series is 'identified by (provider, dataset, series_code)', the description signals this tool is for when you already hold exact identifiers. There is no explicit when-to-use, no exclusion, and no named alternative such as find_series for discovering a series code.

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.