Crypto, web, finance and app data tools

Macro Market Snapshot

markets_snapshot

Latest daily values of the dollar index, Fed funds, the Treasury curve (3m-30y) and 10y-2y spread, breakeven inflation, mortgage rates, WTI and Brent oil, natural gas and EUR, GBP, JPY and CNY rates, with 1-day, 1-week and 1-month changes.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 24, 2026

TDQS

B3.4/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden. It does add genuine context by stating the data is 'daily', lists 'latest' values, and specifies the return windows (1-day, 1-week, 1-month), but it says nothing about data source, freshness/lag, units, or rate limits.

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?

A single dense sentence with no filler, and every listed series earns its place by defining coverage. It is a bit packed into one run-on list rather than front-loading a plain statement of purpose, which keeps it from a 5.

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-value structure need not be explained, and zero parameters make invocation trivial. What remains missing is differentiation from sibling macro/yield/FX tools, which is a meaningful gap for an agent choosing among many near-overlapping options.

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?

Zero parameters, so there is nothing to clarify; baseline 4 applies. The description's role here is purely scope framing rather than argument guidance.

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 states a specific resource (a macro market snapshot) and enumerates exactly which series it covers, so an agent knows precisely what data comes back. It does not distinguish the tool from overlapping siblings such as us_treasury_yields, fx_rates, or central_bank_rates, which is where it falls short of a 5.

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?

There is no statement of when to use this tool, when not to, or which sibling to pick for a narrower need (e.g. Treasury curve only vs. this broad macro bundle). The name and scope imply a use case, but the agent is left to infer it.

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

All Crypto, web, finance and app data tools 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?