reference-data

get_series

Read-onlyIdempotent

PAID ($0.003). Current value of a reference series — e.g. series=policy-rate, vat, minimum-wage. Every value carries its official source citation, effective date, last-confirmed date and staleness flag. Pass api_key if you have one (instant card checkout at /pricing); otherwise the response explains how to pay via x402. Every BR series is free to try. After a 200, bind get_changes (free poll) or register_alert (HMAC push; Register: $0 · Delivery after trial: $0.05) on this series so a later gazette does not silently retire the value.

Input Schema

Name	Required	Description
`series`	Yes	Series id, e.g. policy-rate, vat, minimum-wage
`api_key`	No	API key (bypasses x402; metered for invoicing)
`country`	Yes	ISO country code

Output Schema

Name	Required	Description
`unit`	No
`error`	No	Present on a free refusal or error; no charge
`notes`	No
`stale`	No
`value`	No
`series`	No
`source`	No
`country`	No
`no_charge`	No
`price_usd`	No
`confidence`	No
`disclaimer`	No
`how_to_pay`	No
`bind_series`	No
`explanation`	No
`label_basis`	No	Inputs and the rule ids that produced the two labels
`x_next_bind`	No
`http_endpoint`	No
`coverage_label`	No	How much of the question is covered: ready = complete; partial = held with a disclosed limitation or default; gap = no number served. Rules at /label-rules
`effective_from`	No
`last_confirmed`	No
`confidence_label`	No	Evidence verdict derived from source type, verification age and the stale flag (answers: the weakest series read). Rules at /label-rules
`payment_required`	No	true when the call needs payment; how_to_pay explains x402 or card

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 17, 2026
- removedOutput schema / properties / label_basis / properties / source_type / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / label_basis / properties / source_type / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / label_basis / properties / verification_age_days / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / label_basis / properties / verification_age_days / type
```
Added value: +[
+  "number",
+  "null"
+]
```

Changed3 schema fields changedOct 13, 2026

addedOutput schema / properties / confidence_label

Added value: +{
+  "description": "Evidence verdict derived from source type, verification age and the stale flag (answers: the weakest series read). Rules at /label-rules",
+  "enum": [
+    "high",
+    "medium",
+    "low"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / coverage_label

Added value: +{
+  "description": "How much of the question is covered: ready = complete; partial = held with a disclosed limitation or default; gap = no number served. Rules at /label-rules",
+  "enum": [
+    "ready",
+    "partial",
+    "gap"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / label_basis

Added value: +{
+  "additionalProperties": {},
+  "description": "Inputs and the rule ids that produced the two labels",
+  "properties": {
+    "confidence_reasons": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "coverage_reasons": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "inputs": {
+      "items": {},
+      "type": "array"
+    },
+    "rules": {
+      "type": "string"
+    },
+    "rules_version": {
+      "type": "string"
+    },
+    "source_type": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "stale": {
+      "type": "boolean"
+    },
+    "verification_age_days": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedOct 12, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "description": "Current value of one series with source, effective date, last_confirmed and stale flag",
+  "properties": {
+    "bind_series": {},
+    "confidence": {},
+    "country": {
+      "type": "string"
+    },
+    "disclaimer": {},
+    "effective_from": {},
+    "error": {
+      "description": "Present on a free refusal or error; no charge"
+    },
+    "explanation": {},
+    "how_to_pay": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "http_endpoint": {
+      "type": "string"
+    },
+    "last_confirmed": {},
+    "no_charge": {
+      "type": "boolean"
+    },
+    "notes": {},
+    "payment_required": {
+      "description": "true when the call needs payment; how_to_pay explains x402 or card",
+      "type": "boolean"
+    },
+    "price_usd": {
+      "type": "number"
+    },
+    "series": {
+      "type": "string"
+    },
+    "source": {},
+    "stale": {
+      "type": "boolean"
+    },
+    "unit": {},
+    "value": {},
+    "x_next_bind": {}
+  },
+  "type": "object"
+}

Changed1 schema field changedJul 24, 2026

changedInput schema / properties / country / enum

Previous value: -[
-  "ar",
-  "bb",
-  "bo",
-  "br",
-  "bz",
-  "cl",
-  "co",
-  "cr",
-  "do",
-  "ec",
-  "gt",
-  "hn",
-  "jm",
-  "mx",
-  "ni",
-  "pa",
-  "pe",
-  "py",
-  "sv",
-  "tt",
-  "uy"
-]New value: +[
+  "ar",
+  "bb",
+  "bo",
+  "br",
+  "bz",
+  "cl",
+  "co",
+  "cr",
+  "do",
+  "ec",
+  "gt",
+  "gy",
+  "hn",
+  "jm",
+  "mx",
+  "ni",
+  "pa",
+  "pe",
+  "py",
+  "sv",
+  "tt",
+  "uy"
+]

Changed1 schema field changedJul 24, 2026

changedInput schema / properties / country / enum

Previous value: -[
-  "ar",
-  "bo",
-  "br",
-  "cl",
-  "co",
-  "cr",
-  "do",
-  "ec",
-  "gt",
-  "hn",
-  "mx",
-  "pa",
-  "pe",
-  "py",
-  "sv",
-  "uy"
-]New value: +[
+  "ar",
+  "bb",
+  "bo",
+  "br",
+  "bz",
+  "cl",
+  "co",
+  "cr",
+  "do",
+  "ec",
+  "gt",
+  "hn",
+  "jm",
+  "mx",
+  "ni",
+  "pa",
+  "pe",
+  "py",
+  "sv",
+  "tt",
+  "uy"
+]

Changed1 schema field changedJul 20, 2026

changedInput schema / properties / country / enum

Previous value: -[
-  "ar",
-  "br",
-  "cl",
-  "co",
-  "cr",
-  "do",
-  "ec",
-  "gt",
-  "mx",
-  "pe",
-  "py",
-  "uy"
-]New value: +[
+  "ar",
+  "bo",
+  "br",
+  "cl",
+  "co",
+  "cr",
+  "do",
+  "ec",
+  "gt",
+  "hn",
+  "mx",
+  "pa",
+  "pe",
+  "py",
+  "sv",
+  "uy"
+]

First observedJul 17, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Beyond the annotations (readOnly, idempotent, non-destructive, open-world), the description discloses pricing ($0.003), two distinct auth/payment paths (api_key card checkout vs x402), a free tier (BR series), and what each returned value contains (source citation, effective date, last-confirmed date, staleness flag). This is rich, non-redundant behavioral detail.

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 price and core purpose are front-loaded, and sentences are dense with real information. The trailing sentence carries pricing detail for other tools ($0.05 delivery) that is marginally relevant to calling this tool, slightly diluting focus.

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 paid endpoint with two auth paths, the description covers cost, payment mechanics, free-tier scope, and follow-on actions, and an output schema already documents return values. The one remaining gap is that it never explicitly contrasts this tool with get_series_history or list_series.

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%, so the schema already documents series, api_key and the country enum; baseline is 3. The description only mildly enriches this — it restates the series examples already present in the schema and adds the x402 fallback context — and says nothing about the country parameter.

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 states a specific verb and resource — 'Current value of a reference series' — and lists concrete series examples (policy-rate, vat, minimum-wage). The word 'Current' implicitly differentiates it from the sibling get_series_history, but it never names that sibling, so the differentiation is left to inference.

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

Usage Guidelines4/5

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

It gives clear operational context: pass api_key if you have one, otherwise pay via x402, and after a 200 bind get_changes or register_alert. However, it offers no explicit guidance on when to call get_series versus get_series_history, list_series, compare_series, or get_snapshot.

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

All reference-data 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?