JMT x402 MCP Server

macro_dashboard

Fetch macro economic data: Treasury yields, CPI, Fed, and LLM commentary. Pay per call via x402 on Base mainnet.

Instructions

Macro economic dashboard — Treasury yields + CPI + Fed + LLM commentary. Price: $0.04/call via x402 (USDC on Base mainnet).

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": "macro_dashboard"
  }
}

Input Schema

Name	Required	Description	Default
`region`	No	Region (default: US)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 13, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It discloses the cost and payment method ($0.04/call via x402 on Base mainnet) but does not describe error behavior, rate limits, authentication needs, or data freshness. The tool's behavior beyond contents is opaque.

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?

Two sentences with no redundancy. First sentence states the tool's content; the second states the cost. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has no output schema, but the description does not explain the output format (e.g., whether it's a summary, table, or JSON). It lists contents but not structure. Missing details on error cases and data sources.

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?

The schema covers the one parameter (region) with a description, so baseline is 3. The tool description does not add extra meaning (e.g., possible values or format), but it's adequate given full schema coverage.

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 clearly states the tool provides a macro economic dashboard with Treasury yields, CPI, Fed, and LLM commentary. It distinguishes from siblings like treasury_yields (likely only yields) and market_pulse (broader market). However, it lacks a specific verb indicating the action (e.g., 'get', 'retrieve').

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives. The description does not mention prerequisites, limitations, or when not to use it. The price mention is not usage guidance.

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