Skip to main content
Glama

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

market-pulse

[x402 paid: $0.002 USDC on Base] Market snapshot in one call: multi-coin prices + Fear & Greed + latest Base block. One payment replaces three. 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": "market-pulse"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolsNoexample: BTC,ETH

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations available, the description carries the full burden and does well: it discloses the x402 payment requirement, the exact price (0.002 USDC on Base), and the non-obvious fact that tools/call returns a live payment challenge rather than data. It stops short of describing what is returned after payment succeeds or any freshness/caching behavior.

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?

Three tight sentences with the payment caveat front-loaded in a bracketed tag, then the value proposition, then the call-flow note. The bracket syntax is dense but each clause earns its place; only minor polish would improve readability.

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-optional-param tool with no output schema and no annotations, the description covers purpose, price, and the payment-challenge flow. The remaining gap is what the response looks like after payment and how the tool behaves with no symbols supplied.

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% and the single param already shows 'example: BTC,ETH', so the baseline is 3. The description adds nothing about the symbols parameter (e.g. default behavior when omitted, even though 0 params are required), so it does not exceed the schema's contribution.

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?

States a specific composite resource: 'Market snapshot in one call: multi-coin prices + Fear & Greed + latest Base block.' The phrase 'One payment replaces three' implicitly distinguishes it from the single-datum siblings (crypto-price, fear-greed, block-number) without naming them, which is clear but not fully explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'One payment replaces three' implies the selection rule (use this when you want all three data points in a single paid call), but there is no explicit when-not guidance, no comparison of cost vs three separate calls, and no mention of what happens if the caller supplies no symbols.

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