StatCite

Get a raw series by explicit id

get_series

Read-onlyIdempotent

Fetch economic time series by explicit ID from World Bank, IMF, Caribstat, or DBnomics, with full citation and optional year filters or transforms.

Instructions

Fetch any supported series by explicit id: 'worldbank/' (needs country), 'imf/' (needs country; current-vintage IMF WEO/Fiscal Monitor via the DataMapper API), 'caribstat/<ECCB|CBB>//' (Eastern Caribbean Central Bank and Central Bank of Barbados tables, including Anguilla and Montserrat, which the World Bank does not report; find ids with search_indicators), or 'dbnomics///' (IMF WEO, OECD, Eurostat and more via DBnomics, dated editions, e.g. 'WEO:2025-04', for vintage-pinned reproducibility). 'fred/' ids are recognized only so the service can return an explanatory disabled response. FRED is permanently disabled here and those ids are never retrievable. Supports year filters and transforms (yoy, pct_change, index). Every response carries a full citation. Prefer get_indicator for common indicators.

Input Schema

TableJSON Schema

Name	Required	Description
`country`	No	Required for worldbank/* series.
`end_year`	No
`series_id`	Yes	e.g. 'worldbank/NY.GDP.MKTP.KD.ZG', 'imf/NGDP_RPCH', 'dbnomics/IMF/WEO:latest/BRB.NGDP_RPCH.pcent_change'.
`transform`	No
`start_year`	No
`latest_only`	No	Return only the most recent non-null observation.
`strict_source`	No	Reproducibility mode for registry-key ids: never substitute the fallback source. No effect on explicit source-prefixed ids (they already pin one source).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`name`	Yes
`unit`	No
`notes`	Yes
`country`	No
`citation`	Yes
`frequency`	No
`series_id`	Yes
`observations`	Yes
`fallback_used`	No
`stale_primary`	No
`fallback_reason`	No
`stale_primary_years`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.14.0Sep 20, 2026
- addedOutput schema / properties / stale_primary
```
Added value: +{
+  "type": "boolean"
+}
```
- addedOutput schema / properties / stale_primary_years
```
Added value: +{
+  "type": "number"
+}
```

Changed2 schema fields changedv1.12.2Sep 13, 2026

addedInput schema / properties / latest_only

Added value: +{
+  "description": "Return only the most recent non-null observation.",
+  "type": "boolean"
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "citation": {
+      "additionalProperties": true,
+      "properties": {
+        "citation_text": {
+          "type": "string"
+        },
+        "license": {
+          "type": "string"
+        },
+        "retrieved_at": {
+          "type": "string"
+        },
+        "series_id": {
+          "type": "string"
+        },
+        "source": {
+          "type": "string"
+        },
+        "source_url": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "source",
+        "series_id",
+        "source_url",
+        "license",
+        "retrieved_at",
+        "citation_text"
+      ],
+      "type": "object"
+    },
+    "country": {
+      "additionalProperties": true,
+      "properties": {
+        "iso3": {
+          "type": "string"
+        },
+        "name": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "iso3",
+        "name"
+      ],
+      "type": "object"
+    },
+    "fallback_reason": {
+      "enum": [
+        "transient",
+        "definitive"
+      ],
+      "type": "string"
+    },
+    "fallback_used": {
+      "type": "boolean"
+    },
+    "frequency": {
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    },
+    "notes": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "observations": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "note": {
+            "type": "string"
+          },
+          "period": {
+            "type": "string"
+          },
+          "value": {
+            "type": [
+              "number",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "period",
+          "value"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "series_id": {
+      "type": "string"
+    },
+    "unit": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "series_id",
+    "name",
+    "observations",
+    "citation",
+    "notes"
+  ],
+  "type": "object"
+}

First observedJul 29, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses important behavior: FRED ids return an explanatory disabled response rather than data, every response carries a full citation, and strict_source controls fallback substitution for reproducibility. These are genuine operational details not available from annotations alone.

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?

The description is longer than average, but nearly every clause carries necessary information about id formats, source behavior, and usage routing. It is front-loaded with the main action and the detail is organized into scannable clauses rather than rambling.

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 tool with seven parameters and multiple source-specific formats, the description covers the id schemes, country preconditions, disabled FRED case, filters and transforms, citation behavior, and the preferred sibling tool. Since an output schema is present, return-value formatting does not need to be restated.

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?

With only 57% schema coverage, the description compensates substantially by documenting series_id formats, country requirements per source, vintage pinning, and transform support. It leaves some details, such as exact start_year/end_year boundaries, to inference, but the most complex parameter surface is well explained.

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?

The description opens with a specific verb and resource: 'Fetch any supported series by explicit id.' It goes beyond a bare statement by enumerating the supported id formats and ends with routing to get_indicator, which distinguishes it from a likely sibling tool.

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?

The description gives explicit routing guidance: use this tool for explicit source-prefixed ids, use get_indicator for common indicators, and use search_indicators to find caribstat ids. It also warns that FRED ids are permanently disabled, preventing futile calls.

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

Deploy Server