Skip to main content
Glama

MNOGO DENEG — pay-per-call crypto & AI APIs (x402)

tool_crypto_market-pulse

[x402 paid: $0.002 USDC on Base] Prices for a symbol list + Fear & Greed + latest Base block in one response. tools/call returns the live payment challenge.

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": "tool_crypto_market-pulse"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolsNoexample: BTC,ETH

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does the most important part: it discloses that the call is metered ($0.002 USDC on Base via x402) and that tools/call returns a live payment challenge, which is exactly the non-obvious behavior an agent must handle. It does not cover failure modes, whether the challenge is reusable, or latency, keeping it short of a 5.

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?

Two compact sentences plus a bracketed cost tag, with the payment requirement front-loaded before the payload description. Nothing is padded, though the bracket prefix and the 'tools/call' phrasing are slightly jargon-heavy for an agent scanning quickly.

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 one-parameter, no-annotation tool with no output schema, the description substitutes well by enumerating the three data blocks returned and the payment flow. The remaining gap is that it never says what happens to the symbols parameter when omitted, given that zero parameters are required.

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?

Schema coverage is 100% for the single optional 'symbols' parameter, including an example format, so the schema already does the documentation work. The description only restates that a symbol list is expected and adds no formatting or defaulting detail beyond the schema example.

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 names the concrete payload: prices for a symbol list, Fear & Greed, and the latest Base block, returned together in one response. That composite scope distinguishes it from single-purpose siblings like tool_crypto_price or tool_crypto_feargreed, though the operative verb is implicit ('Prices for...') rather than stated outright.

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 explicit when-to-use or when-not-to-use guidance, and no sibling is named as an alternative despite several single-purpose price and sentiment tools existing. The bundling value is only inferable from the phrase 'in one response', leaving the agent to guess whether to call this or a narrower 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