Skip to main content
Glama
Sign In

reference-data

by dev.asiaref
OverviewDiscussionsAdmin

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 JP 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

NameRequiredDescriptionDefault
seriesYesSeries id, e.g. policy-rate, vat, minimum-wage
api_keyNoAPI key (bypasses x402; metered for invoicing)
countryYesISO country code

Output Schema

NameRequiredDescriptionDefault
unitNo
errorNoPresent on a free refusal or error; no charge
notesNo
staleNo
valueNo
seriesNo
sourceNo
countryNo
no_chargeNo
price_usdNo
confidenceNo
disclaimerNo
how_to_payNo
bind_seriesNo
explanationNo
label_basisNoInputs and the rule ids that produced the two labels
x_next_bindNo
http_endpointNo
coverage_labelNoHow 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_fromNo
last_confirmedNo
confidence_labelNoEvidence verdict derived from source type, verification age and the stale flag (answers: the weakest series read). Rules at /label-rules
payment_requiredNotrue when the call needs payment; how_to_pay explains x402 or card

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • 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"
+]
  2. Changed3 schema fields changed
    • 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"
+}
  3. Changed1 schema field changed
    • 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"
+}
  4. Changed1 schema field changed
    • changedInput schema / properties / country / enum
      Previous value: -[
-  "ae",
-  "bd",
-  "bh",
-  "cn",
-  "hk",
-  "id",
-  "il",
-  "in",
-  "jp",
-  "kr",
-  "kw",
-  "kz",
-  "lk",
-  "my",
-  "om",
-  "ph",
-  "pk",
-  "qa",
-  "sa",
-  "sg",
-  "th",
-  "tr",
-  "tw",
-  "vn"
-]New value: +[
+  "ae",
+  "bd",
+  "bh",
+  "cn",
+  "hk",
+  "id",
+  "il",
+  "in",
+  "iq",
+  "jo",
+  "jp",
+  "kr",
+  "kw",
+  "kz",
+  "lk",
+  "my",
+  "np",
+  "om",
+  "ph",
+  "pk",
+  "qa",
+  "sa",
+  "sg",
+  "th",
+  "tr",
+  "tw",
+  "uz",
+  "vn"
+]
  5. Changed1 schema field changed
    • changedInput schema / properties / country / enum
      Previous value: -[
-  "ae",
-  "bd",
-  "bh",
-  "cn",
-  "hk",
-  "id",
-  "il",
-  "in",
-  "jp",
-  "kr",
-  "kw",
-  "my",
-  "om",
-  "ph",
-  "pk",
-  "qa",
-  "sa",
-  "sg",
-  "th",
-  "tr",
-  "tw",
-  "vn"
-]New value: +[
+  "ae",
+  "bd",
+  "bh",
+  "cn",
+  "hk",
+  "id",
+  "il",
+  "in",
+  "jp",
+  "kr",
+  "kw",
+  "kz",
+  "lk",
+  "my",
+  "om",
+  "ph",
+  "pk",
+  "qa",
+  "sa",
+  "sg",
+  "th",
+  "tr",
+  "tw",
+  "vn"
+]
  6. Changed1 schema field changed
    • changedInput schema / properties / country / enum
      Previous value: -[
-  "ae",
-  "bd",
-  "cn",
-  "hk",
-  "id",
-  "in",
-  "jp",
-  "kr",
-  "my",
-  "ph",
-  "pk",
-  "qa",
-  "sa",
-  "sg",
-  "th",
-  "tr",
-  "tw",
-  "vn"
-]New value: +[
+  "ae",
+  "bd",
+  "bh",
+  "cn",
+  "hk",
+  "id",
+  "il",
+  "in",
+  "jp",
+  "kr",
+  "kw",
+  "my",
+  "om",
+  "ph",
+  "pk",
+  "qa",
+  "sa",
+  "sg",
+  "th",
+  "tr",
+  "tw",
+  "vn"
+]
  7. Changed1 schema field changed
    • changedInput schema / properties / country / enum
      Previous value: -[
-  "bd",
-  "id",
-  "in",
-  "jp",
-  "kr",
-  "my",
-  "ph",
-  "sg",
-  "th",
-  "vn"
-]New value: +[
+  "ae",
+  "bd",
+  "cn",
+  "hk",
+  "id",
+  "in",
+  "jp",
+  "kr",
+  "my",
+  "ph",
+  "pk",
+  "qa",
+  "sa",
+  "sg",
+  "th",
+  "tr",
+  "tw",
+  "vn"
+]
  8. Changed1 schema field changed
    • changedInput schema / properties / country / enum
      Previous value: -[
-  "in",
-  "jp",
-  "kr",
-  "ph",
-  "sg"
-]New value: +[
+  "bd",
+  "id",
+  "in",
+  "jp",
+  "kr",
+  "my",
+  "ph",
+  "sg",
+  "th",
+  "vn"
+]
  9. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive), and the description adds substantial non-obvious context: pay-per-call pricing, the auth/checkout mechanism, the free-tier carve-out, and exactly what each returned value carries (source citation, effective date, last-confirmed date, staleness flag). This is well beyond what structured fields provide.

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 the price and purpose, then layers citation detail, auth handling, and follow-up tools. Dense but nearly every sentence carries operational information; the parenthetical pricing for register_alert is slightly cluttered but earns its place for cost-aware agents.

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?

An output schema exists, yet the description still flags the important return fields, and it covers payment prerequisites, trial limits, and the intended next step. Nothing needed to invoke this tool correctly is missing.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema does not: api_key bypasses x402 and is metered for invoicing, and series is illustrated with real ids. country is left to its enum with no added semantics.

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+resource ('Current value of a reference series') and immediately grounds it with concrete series ids (policy-rate, vat, minimum-wage). An agent can distinguish it from get_series_history and list_series without opening either schema.

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?

Explains payment paths (api_key vs x402), the free JP trial, and names follow-up siblings (get_changes, register_alert) with the condition 'after a 200'. It stops short of explicitly contrasting with get_series_history for historical values, so routing between the two read tools is inferred rather than stated.

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

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