Skip to main content
Glama

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

tool_token_verdict

[x402 paid: $0.002 USDC on Base] Analyst-grade token verdict: live price/liquidity/volume from DexScreener + Fear & Greed + LLM conclusion with risk score 0-100. Three sources, one call. 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_token_verdict"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressNoexample: 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913

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 present, the description carries the full load and does disclose two non-obvious behaviors: the tool is metered at $0.002 USDC on Base via x402, and 'tools/call returns the live payment challenge' rather than a result. That payment-gate detail is exactly the kind of trait an agent cannot get from the schema. It stops short of saying what happens on an invalid or missing address.

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 cost surfaced first and the multi-source value proposition up front; nothing is filler. The parenthetical pricing prefix is dense but earns its position given the payment gate.

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 and no annotations, the description does the necessary work: it enumerates the three data sources, the risk-score range, and the payment-challenge return path. What remains unexplained is the optionality of the address parameter and the response shape after payment succeeds.

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 'address' parameter is fully documented with an example, so the description need not restate it. However, the tool marks zero required parameters, and the description never clarifies whether the address is optional or what the tool returns without it – a meaningful omission for a one-parameter tool.

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 deliverable precisely – an 'Analyst-grade token verdict' aggregating DexScreener price/liquidity/volume, Fear & Greed, and an LLM conclusion with a 0-100 risk score. 'Three sources, one call' implicitly separates it from single-source siblings like tool_token_dexscreener and tool_crypto_feargreed, though it never names an alternative outright.

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?

Usage is only implied: the aggregation framing suggests picking this over stacking the individual data tools, and the x402 price tag implies a paid path. There is no explicit when-to-use, when-not-to-use, or named alternative, so the agent must infer routing.

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