Skip to main content
Glama

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

ai-token-audit

[x402 paid: $0.010 USDC on Base] Token audit in one call: DexScreener liquidity/price/volume + Fear & Greed + LLM risk verdict fused into one JSON. One payment, three sources. 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": "ai-token-audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenNoexample: 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913

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 real work: it discloses the price ($0.010 USDC on Base) and, critically, that 'tools/call returns the live payment challenge' — meaning a first call yields a 402-style challenge rather than audit data. That is high-value MCP-specific behavior an agent would otherwise not anticipate. It still omits what happens on failed/expired payment and whether the charged call is retried automatically.

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 no waste; the paid-access bracket is front-loaded so cost is seen before commitment, and the source list is compact. Minor deduction because the payment mechanics sentence sits after the value proposition rather than being grouped with the pricing note.

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

Completeness5/5

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

There is no output schema, but the description enumerates what the fused JSON contains (liquidity/price/volume, Fear & Greed, risk verdict) and explains payment flow, which is what an agent needs for a single-parameter tool. The only residual gap is chain coverage and the oddly optional `token` field, neither of which blocks correct invocation.

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?

One parameter at 100% schema coverage, so the schema already documents the `token` field and its example address. The description adds nothing about the parameter — not that it is technically optional (required=0), nor which chains are accepted, even though the single example address is a Base contract. Baseline 3 is correct when the schema does the lifting.

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 verb+resource ('Token audit') and decomposes it into its three constituents: DexScreener liquidity/price/volume, Fear & Greed, and an LLM risk verdict fused into one JSON. That composite framing implicitly distinguishes it from the narrower siblings (token-price, fear-greed, token-safety-pack), though it never names an alternative explicitly.

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 by 'in one call' and 'One payment, three sources' — an agent can infer this is the all-in-one option when it wants several signals at once. There is no explicit when-to-use, when-not-to-use, or routing to the simpler sibling tools (token-price, token-safety-pack) for single-signal needs.

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