Skip to main content
Glama

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

tool_token_dexscreener

[x402 paid: $0.001 USDC on Base] DexScreener pairs for any token: price, liquidity, volume, txns. Body: {address}. 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_dexscreener"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose genuinely useful behavior beyond the schema: a fixed $0.001 USDC price on Base and a challenge-response payment flow returned by tools/call. It omits what happens after payment (return shape, failure modes, whether cost is charged per call or per retry), leaving a gap for a paid tool.

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?

Four compact clauses, with the cost tag front-loaded, then purpose, then input, then payment mechanics. No filler, though the bracket-notation price tag and the payment sentence slightly crowd out the operational detail.

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?

For a paid tool with no annotations, no output schema, and an empty input schema, the description covers cost, input field name, and the payment handshake, which is the minimum an agent needs. It is still incomplete on supported chains, the returned data shape, and error/refund behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema declares zero properties, so the description's 'Body: {address}' is the only source of argument information and adds real value. It is still thin: it does not say whether the address is a token address or pair address, nor which chains are supported, and it conflicts with the empty schema.

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 resource (DexScreener pairs for any token) and the exact fields returned (price, liquidity, volume, txns), which is far more specific than a restated name. It does not explicitly distinguish itself from near-neighbours like token-price or tool_token_verdict, so it stops short of a 5.

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 implied by 'for any token', and the payment mechanics ('tools/call returns the live payment challenge') tell the agent how the call sequence works. However, there is no statement of when to prefer this over token-price or the safety tools, and no prerequisites or exclusions.

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