Skip to main content
Glama

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

tool_crypto_price

[x402 paid: $0.001 USDC on Base] Spot price of any coin by symbol. 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_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolNoexample: BTC

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description does the heavy lifting on the most distinctive trait: it is an x402 micropayment tool costing $0.001 USDC on Base, and tools/call returns a live payment challenge. That is genuinely useful behavioral context. It still omits what an unpaid call returns, whether calls are metered or rate-limited, and how symbols that fail to resolve behave.

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 short sentences with no filler. The payment banner is front-loaded rather than the purpose, but both fit in one line, so nothing meaningful is buried.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no annotations and no output schema, the description should describe the shape of the successful result (for example, price and currency), but it never does. It covers the payment prerequisite but leaves the return value and error behavior undocumented.

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?

Single parameter at 100% schema coverage, so the schema already documents the symbol and gives a BTC example. The description adds that any coin symbol is accepted, which is slight but real added meaning. Baseline 3 is appropriate given the schema does the work.

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 resource and lookup key: 'Spot price of any coin by symbol'. An agent knows exactly what it returns at a glance. However, it does not differentiate itself from siblings such as crypto-price, token-price, and usd-price, which plausibly do the same thing.

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 when-to-use or when-not-to-use guidance and no mention of when to prefer the sibling price tools. The only contextual signal is the payment cost, which implies 'use sparingly' but is never stated as 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