Stablecoin Gateways

US Treasury Yields and CPI

us_rates_macro

Read-onlyIdempotent

US Treasury yields and inflation data: daily Treasury par yield curve (1-month to 30-year) plus BLS CPI, core CPI, unemployment rate and nonfarm payrolls for the last 13 months with year-over-year change. Use when a finance agent needs current US interest rates, inflation or jobs data. Sources: US Treasury, BLS (public). Signed receipt. Price: $0.002 per call via x402 (USDC on Base or XRP on XRPL). The response includes a provenance block (sg-provenance/1): each fact carries its source, source URL, retrieval time and limits; evidence only, no score, rating or verdict. Example arguments: {"series":"treasury,cpi"}.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "us_rates_macro"
  }
}

Input Schema

Name	Required	Description	Default
`series`	No	Comma list of treasury,cpi,core_cpi,unemployment,payrolls; default all

Output Schema

Name	Required	Description	Default
`data`	No	US Treasury par yield curve and BLS CPI, core CPI, unemployment and payrolls series
`receipt`	No	Ed25519-signed, hash-chained receipt; verify free with the verify_receipt tool or POST /v1/verify-receipt. New receipts carry a signed `evidence` object: service_version, data_timestamp, validation, terms_version, terms_hash, provenance_hash.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 24, 2026

addedOutput schema / properties / data / properties / provenance

Added value: +{
+  "description": "The response includes a `provenance` block (sg-provenance/1): each fact carries its source, source URL, retrieval time and limits; evidence only, no score, rating or verdict."
+}

Changed1 schema field changedOct 24, 2026

changedOutput schema / properties / receipt / description

Previous value: -"Ed25519-signed, hash-chained receipt; verify free with the verify_receipt tool or POST /v1/verify-receipt"New value: +"Ed25519-signed, hash-chained receipt; verify free with the verify_receipt tool or POST /v1/verify-receipt. New receipts carry a signed `evidence` object: service_version, data_timestamp, validation, terms_version, terms_hash, provenance_hash."

Changed1 schema field changedOct 22, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Paid result: { data, receipt }. Unpaid calls return an x402 PaymentRequired object instead (isError: true).",
+  "properties": {
+    "data": {
+      "description": "US Treasury par yield curve and BLS CPI, core CPI, unemployment and payrolls series",
+      "properties": {
+        "cpi": {},
+        "retrieved_from_cache_as_of": {},
+        "series": {},
+        "sources": {},
+        "treasury_par_yield_curve": {}
+      }
+    },
+    "receipt": {
+      "description": "Ed25519-signed, hash-chained receipt; verify free with the verify_receipt tool or POST /v1/verify-receipt"
+    }
+  },
+  "type": "object"
+}

First observedOct 22, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond annotations, it discloses sources (US Treasury, BLS), a signed receipt, per-call pricing via x402, accepted payment chains/assets, the provenance block format, and an explicit 'evidence only, no score, rating or verdict' limitation. This is unusually rich behavioral and operational context.

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 front-loaded with the data scope and use case, then pricing and provenance details. It is fairly dense but appropriate for a paid, provenance-bearing data tool; little is wasteful, though the pricing/provenance details make it longer than a typical definition.

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 single-parameter, read-only data tool with an output schema, the description covers data scope, time range, sources, pricing, payment mechanics, provenance format, and limits. An agent can decide whether to call it and what to expect without opening other fields.

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% and already documents the only parameter, so the baseline is 3. The description adds a concrete example argument and reinforces the valid series names, giving slight practical value beyond the schema.

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 states a specific data resource — daily US Treasury par yield curve plus BLS CPI, core CPI, unemployment, and payrolls — and specifies the 13-month window with year-over-year change. It is clearly distinguishable from FX-focused siblings such as fx_reference_rates or fx_convert, and from sec_company_facts.

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 a clear use case: 'Use when a finance agent needs current US interest rates, inflation or jobs data.' It does not explicitly name alternatives or when-not-to-use conditions, but the domain is specific enough that overlap with siblings is limited.

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

All Stablecoin Gateways 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?