Crypto, web, finance and app data tools

Exchange Spot Ticker

exchange_ticker

Live spot price of a crypto pair on Coinbase and Kraken: bid, ask, last, 24h open/high/low and volume, and the price gap between the two exchanges. Use for an exact executable price or a quick arbitrage check.

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

Input Schema

Name	Required	Description	Default
`pair`	No		BTC-USD

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 22, 2026

TDQS

A4/5.0

Behavior3/5

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

No annotations, so the description carries full burden. It conveys the multi-source read and the exact fields, but omits behavioral details such as what happens if one exchange is unavailable, rate limits, or the default pair. For a simple read it is acceptable, but not complete.

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 tight sentences with zero waste: the first specifies content and sources, the second gives usage. Front-loaded and well-organized.

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 needn't be spelled out, and the description covers purpose, sources, and use. The only gap is the pair format/default, minor for a one-parameter read tool.

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?

Only one parameter (pair) with 0% schema description coverage. The description references 'a crypto pair,' implying the parameter's role, but does not give the expected format (e.g., BTC-USD) or mention the BTC-USD default, leaving the schema to carry undocumented weight.

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 specific verb+resource (live spot price of a crypto pair) and enumerates the exact data returned (bid, ask, last, 24h OHLC, volume, cross-exchange gap) and the two sources (Coinbase, Kraken). This clearly distinguishes it from history/candles siblings like crypto_price_history and crypto_candles.

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?

Explicitly says 'Use for an exact executable price or a quick arbitrage check,' which gives a clear selection context. It does not, however, name alternatives or state when to prefer a different sibling (e.g., price history).

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?