Skip to main content
Glama

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

token-price

[x402 paid: $0.005 USDC on Base] Price, liquidity and 24h volume of ANY token by contract address (DexScreener, ?address=0x...). 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": "token-price"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/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 behavioral burden and does disclose the critical trait: this is an x402-paid endpoint costing $0.005 USDC on Base, and that tools/call returns a live payment challenge rather than data. It omits what happens after payment (response shape, failure modes), which keeps it from a 5.

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?

Two dense sentences with no filler; the paid-endpoint caveat and the invocation syntax are both front-loaded before any elaboration.

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 zero-parameter, no-annotation, no-output-schema tool, it covers cost, payment flow, data source, returned fields and the address convention. Gaps around chain scoping and post-payment response are minor at this complexity level.

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 is empty, so the description must supply the invocation convention, and it does: the address is passed as ?address=0x... in the DexScreener URL. It still leaves chain selection and multi-chain behaviour unexplained despite claiming ANY token.

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 (token price, liquidity and 24h volume) and scopes it to ANY token identified by contract address, with the data source (DexScreener) named. It does not explicitly distinguish itself from near-neighbours such as crypto-price or tool_token_dexscreener, so the reader must infer the difference.

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: use when you have a contract address and need market data for an arbitrary token. There is no explicit when-not or named alternative, and no statement about what to do when the address is for an unsupported chain, so routing among the many pricing siblings is left to inference.

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