Skip to main content
Glama

Money Reactor — 87 paid x402 APIs via MCP

get_market_pulse

Paid $0.02 (x402, USDC Base): full market snapshot in ONE call — batch USD prices (default BTC/ETH/SOL/XRP/DOGE, optional symbols arg) + Fear & Greed sentiment + latest Base block. One poll replaces three calls; ideal for monitoring loops.

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_market_pulse"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolsNoComma-separated pairs BASE-QUOTE (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, this description carries the full behavioral burden and does disclose the critical trait: a $0.02 charge via x402/USDC on Base, which is effectively the auth/cost model an agent must know before invoking. It also reveals default symbols and the composite nature of the response, but says nothing about failure behavior, whether the fee applies per call regardless of outcome, or the structure of returned data.

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?

One dense sentence, front-loaded with the cost and the core value proposition, then the usage hint. Every clause (price, protocol, contents, defaults, monitoring use) carries distinct information with no filler.

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?

With no output schema, the description must convey what comes back, and it enumerates all three returned components at a conceptual level along with the payment cost. It lacks field-level return shape and error semantics, a minor gap for a single-optional-parameter read tool.

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 coverage is already 100%, so the baseline is 3, but the description adds real meaning the schema lacks: the default symbol set (BTC/ETH/SOL/XRP/DOGE) and the fact that batch pricing is what the symbols argument feeds. The format hint (BASE-QUOTE) remains only in the schema.

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 action and composite resource: a full market snapshot returned in one call, combining USD prices, Fear & Greed sentiment, and the latest Base block. It clearly separates itself from the single-purpose siblings (get_usd_price, get_fear_greed, get_latest_block) by explicitly framing the batch behavior.

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?

"One poll replaces three calls; ideal for monitoring loops" gives a clear context for when this is the right choice, implicitly steering agents away from single-purpose tools. It does not name those alternatives explicitly or state the converse case (when to prefer a cheaper single-value tool), so it stops short of full when/when-not guidance.

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