Skip to main content
Glama

Money Reactor — 87 paid x402 APIs via MCP

get_usd_price

Paid $0.02 (x402, USDC Base): multi-asset USD price snapshot in ONE call — up to 25 pairs (default 10 majors: BTC/ETH/SOL/DOGE/XRP/ADA/AVAX/LINK/LTC/USDC). Batch beats per-pair calls for portfolio and dashboard agents.

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

Input Schema

NameRequiredDescriptionDefault
symbolsNoComma-separated pairs BASE-QUOTE, e.g. BTC-USD,ETH-USD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It usefully reveals the paid cost ($0.02 via x402, USDC Base), the default 10 majors, and the 25-pair maximum. It omits freshness, rate limits, and response format, which are meaningful for a paid price snapshot.

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?

It is a single compact sentence with no filler and front-loads purpose and price. The em-dash and parenthetical density make it slightly harder to scan, but every clause contributes information.

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?

For a low-complexity, single-parameter tool with no output schema, the description covers payment, default behavior, batching limit, and intended audience. The main remaining gap is that it does not describe the snapshot's return fields or freshness.

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 description coverage is 100%, so the schema already explains the comma-separated BASE-QUOTE format. The description adds useful meaning beyond the schema by stating the default symbol set and the maximum of 25 pairs.

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 verb and resource: 'multi-asset USD price snapshot in ONE call' with batching up to 25 pairs. It distinguishes itself from generic 'per-pair calls' but does not name sibling tools such as get_crypto_price or get_coin_convert, so it falls short of full sibling differentiation.

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 clear context for use: 'Batch beats per-pair calls for portfolio and dashboard agents.' That tells an agent when batching is preferable. However, it does not name alternatives explicitly or state when not to use this tool.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources