MCPFax Macro & Market Intelligence

US Treasury yields

us_treasury_yields

Read-onlyIdempotent

US Treasury constant-maturity yields for the 2, 10 and 30 year tenors in percent, the computed 10s2s curve spread with an explicit inverted flag, and the 30-year fixed mortgage rate. IMPORTANT: this is a STORED SNAPSHOT, not a live read — the FRED host blocks Cloudflare Workers (HTTP 520), so it is refreshed out of band. Every response carries snapshot.captured_at and snapshot.age_hours; check them before trading or quoting off these numbers. Costs $0.01 USDC per call via x402 on Base; an unpaid call returns the payment challenge instead of data, and a call that returns no data is never settled so it costs nothing. Equivalent HTTP route: GET /rates.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`as_of`	No	Return the stored capture in effect at this UTC date or ISO timestamp instead of the latest one (append-only history; not subject to the freshness limit) Example: '2026-08-11'.

TDQS

A4.1/5.0

Behavior5/5

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

The description adds substantial behavior beyond the annotations: it is a stored snapshot, refreshed out of band due to FRED blocking Cloudflare Workers, and responses include snapshot.captured_at and snapshot.age_hours. It also discloses the $0.01 USDC cost, payment challenge behavior, and no-data-no-charge guarantee. This aligns with and enriches readOnlyHint and idempotentHint.

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

Conciseness5/5

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

Every sentence earns its place: content summary, snapshot freshness warning, cost/payment behavior, and equivalent HTTP route. The most important caveat is marked IMPORTANT and appears early, and the length is justified by the critical operational details.

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?

With no output schema, the description does enough by naming the exact data series, the snapshot metadata fields, the freshness check, and payment semantics. The optional as_of behavior is fully covered in the schema. An agent has enough context to invoke the tool and interpret the result correctly.

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% for the single optional as_of parameter, including format and an example, so the schema carries the parameter semantics. The tool description does not add parameter-specific meaning, but the snapshot context helps clarify what 'capture in effect' means. Baseline 3 is appropriate.

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 precisely enumerates the returned data: 2/10/30-year constant-maturity yields, the 10s2s spread with inverted flag, and the 30-year mortgage rate. This clearly distinguishes it from sibling tools like fx_reference_rates and defi_yields, although it lacks an explicit verb like 'returns'.

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?

Usage context is implied by the data content, and the snapshot warning tells users to check freshness before trading or quoting. However, it does not explicitly state when to prefer this tool over sibling data tools, name alternatives, or specify exclusions.

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

All MCPFax Macro & Market Intelligence tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0

Disambiguation4/5

Most tools target distinct resources: defi_protocol vs defi_protocols are clearly list-vs-detail, and crypto_spot_prices vs defi_token_prices are explicitly differentiated. The main overlap is prediction_market_search vs polymarket_markets/manifold_markets, but the cross-venue purpose is clearly stated.

Naming Consistency5/5

All tool names use snake_case with a consistent resource-noun pattern (defi_, polymarket_, us_, etc.). Plural/singular variants are logical (defi_protocol vs defi_protocols, polymarket_market vs polymarket_markets), and no unconventional casing or verb-style mixing appears.

Tool Count4/5

18 tools is slightly above the ideal 3-15 range, but the server covers a broad domain (crypto, DeFi, prediction markets, macro, FX, rates), so each tool serves a distinct data type. The count feels justified by the breadth rather than redundant.

Completeness4/5

The surface covers major market intelligence categories well: prices, yields, TVL, prediction markets, macro indicators, and FX. Minor gaps exist (e.g., no equities/commodities, limited macro series, no historical crypto data), but the core workflows for macro and market overview are supported without dead ends.

Resources

Need Help?