Skip to main content
Glama
Sign In

reference-data

by dev.latamref
OverviewDiscussionsAdmin

list_series

Read-onlyIdempotent

FREE. Catalog of all latamref reference-data series: supported countries, series ids, descriptions, freshness metadata and per-series URLs. Call this first to discover what data exists. Paid answer tools accept receipt=true (included in the answer price, no extra USDC) and, on a paid success, return an Ed25519 answer receipt (kind answer_receipt). That receipt is not a series certified extract and is not legal advice. Series certified extracts are GET /v1/certified/{country}/{series} at $0.10 and are not an MCP tool. Verify a receipt with verify_answer_receipt (free, public key only) against /certified/public-key. get_changes is free. get_calendar is free. register_alert registration is free.

Input Schema

NameRequiredDescriptionDefault
detailNoDefault false. Without country, false returns a compact index (country -> series ids). true returns the full catalog, which is large.
countryNoOptional ISO country code. Returns full per-series metadata (source, freshness, bands) for that country only.

Output Schema

NameRequiredDescriptionDefault
noteNo
errorNoPresent on a free refusal or error; no charge
countriesNoCountry entries ({country, name, series}); on an unknown-country refusal, the list of valid codes
no_chargeNo
price_usdNo
disclaimerNo
how_to_payNo
bind_seriesNo
explanationNo
x_next_bindNo
http_endpointNo
payment_requiredNotrue when the call needs payment; how_to_pay explains x402 or card

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / description
      Previous value: -"Catalog: brand metadata plus countries[] (compact: country, name, series ids; with country or detail: full per-series metadata)"New value: +"Catalog: brand metadata plus countries[] (compact: country, name, series ids; with country or detail: full per-series metadata including confidence_label and coverage_label)"
  2. Changed3 schema fields changed
    • addedInput schema / properties / country
      Added value: +{
+  "description": "Optional ISO country code. Returns full per-series metadata (source, freshness, bands) for that country only.",
+  "type": "string"
+}
    • addedInput schema / properties / detail
      Added value: +{
+  "description": "Default false. Without country, false returns a compact index (country -> series ids). true returns the full catalog, which is large.",
+  "type": "boolean"
+}
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "description": "Catalog: brand metadata plus countries[] (compact: country, name, series ids; with country or detail: full per-series metadata)",
+  "properties": {
+    "bind_series": {},
+    "countries": {
+      "description": "Country entries ({country, name, series}); on an unknown-country refusal, the list of valid codes",
+      "items": {},
+      "type": "array"
+    },
+    "disclaimer": {},
+    "error": {
+      "description": "Present on a free refusal or error; no charge"
+    },
+    "explanation": {},
+    "how_to_pay": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "http_endpoint": {
+      "type": "string"
+    },
+    "no_charge": {
+      "type": "boolean"
+    },
+    "note": {
+      "type": "string"
+    },
+    "payment_required": {
+      "description": "true when the call needs payment; how_to_pay explains x402 or card",
+      "type": "boolean"
+    },
+    "price_usd": {
+      "type": "number"
+    },
+    "x_next_bind": {}
+  },
+  "type": "object"
+}
  3. First observed

TDQS

A3.7/5.0
Behavior4/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 real value beyond that: the call is free, the response is a metadata catalog, and detail=true yields a large payload. It also clarifies that paywalled answer receipts and certified extracts are distinct, non-legal-advice artifacts.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening two sentences are tight and front-loaded, but the bulk of the text is about unrelated tools — paid answer receipts, Ed25519 verification, certified extract pricing, and which other tools are free. Those sentences do not earn their place in a listing tool's description and dilute the signal.

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?

An output schema exists, so return values need not be explained, and the rich annotations plus the 'free' and payload-size disclosures give an agent enough to call it correctly. The main gap is the absence of an explicit contrast with get_series, which would complete the discovery-vs-fetch story.

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% and both parameters (detail, country) are fully documented in the schema, including the compact-vs-full tradeoff and the per-country metadata behavior. The description adds no parameter syntax or format detail beyond the schema, so the baseline of 3 applies.

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 concrete verb+resource — a catalog of all latamref reference-data series — and enumerates what it returns (countries, series ids, descriptions, freshness metadata, URLs). 'Call this first to discover what data exists' cleanly separates it from data-fetching siblings like get_series and get_series_history.

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?

'Call this first to discover what data exists' gives a clear sequencing directive, and the mentions of verify_answer_receipt, get_changes, get_calendar and register_alert being free imply routing. However, there is no explicit when-not-to-use guidance and no statement of how this differs from get_series, so usage is more implied than spelled out.

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