Skip to main content
Glama

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

token-safety-pack

[x402 paid: $0.030 USDC on Base] Token safety + market context in ONE call: DexScreener liquidity/volume + Fear & Greed + Base gas + LLM risk verdict. One payment, four 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": "token-safety-pack"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the burden, and it does disclose meaningful behavior: the call is x402-paid at $0.030 USDC on Base and 'tools/call returns the live payment challenge', which tells the agent to expect a payment handshake rather than data on first call. It still omits what happens after payment, whether the result is cached or fresh, and whether retries re-charge.

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 short, dense sentences front-loaded with the price tag and then the value proposition and the payment behavior. Nothing is padded, though the bracketed pricing prefix slightly crowds the lead sentence.

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 complex four-source aggregator with no output schema, no annotations, and no parameters, the description still conveys cost, payment flow, and data provenance. What remains missing is how the token subject is determined and what the returned verdict looks like, which matters given there is no output schema.

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 schema declares zero properties, so there are no parameters to disambiguate and the baseline is 4. That said, the absence of any token identifier is a conceptual gap the description does not address.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names what is aggregated (DexScreener liquidity/volume, Fear & Greed, Base gas, an LLM risk verdict) and frames it as a single bundled call, so the composition is clear. However, it never says which token the safety check applies to, and with zero parameters the agent cannot tell how the subject is selected. It also does not distinguish itself from siblings such as ai-token-audit, tool_token_verdict, or market-pulse beyond 'in ONE call'.

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, four sources' implies this should be used instead of calling the individual DexScreener / fear-greed / base-gas tools separately, which is useful routing context. But there is no explicit 'use this when X, use the single-source tool when Y', and no prerequisites are stated beyond the payment note.

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