Skip to main content
Glama

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

tool_ai_research-pro

[x402 paid: $0.005 USDC on Base] All-in-one token research: live prices + Fear & Greed + fresh news + LLM verdict fused into one JSON. One payment replaces four calls. 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_ai_research-pro"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolNoexample: BTC

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the most consequential behavior: this is an x402 paid tool at $0.005 USDC on Base, and a tools/call triggers a live payment challenge rather than returning data immediately. That is genuinely non-obvious and saves an agent from misreading the first response. It still omits failure modes (insufficient balance), latency/freshness bounds, and anything about the shape of the fused JSON.

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?

Three tight sentences with the payment cost bracketed up front and the four data components listed in one clause. Every sentence carries distinct information — cost, contents, payment mechanics — and there is 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?

For a single-parameter tool with no output schema, the description covers the essentials: what goes in, roughly what comes back ('fused into one JSON'), and the payment handshake on first call. The main gap is that with no output schema, the description could sketch the response keys so an agent knows what to expect from the fused JSON.

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?

There is one parameter at 100% schema coverage, where the schema already documents it with 'example: BTC'. The description adds no meaning beyond that — no note on case sensitivity, asset coverage, or what happens when the optional symbol is omitted. Baseline 3 applies since 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?

The description uses a concrete verb and resource — 'All-in-one token research' — and enumerates the four fused components (live prices, Fear & Greed, news, LLM verdict), so the agent knows exactly what it gets. It doesn't name the sibling tools it overlaps with (e.g. tool_token_verdict, tool_crypto_price), leaving the agent to infer the aggregation angle from 'replaces four calls' rather than an explicit comparison.

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 four calls' implies the when-to-use condition: pick this when you want all four data points together instead of separate calls. But there are no explicit exclusions, no guidance on when a cheaper single-purpose sibling is preferable, and no prerequisites beyond the payment note — usage is implied rather than stated.

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