Skip to main content
Glama

Token verdict

token_verdict
Read-onlyIdempotent

Screen a token's structural risks before investigating a trade. Paid HTTP offer: $0.02 USDC. This tool returns free x402 payment requirements; it does not execute or pay for the offer.

Input Schema

NameRequiredDescriptionDefault
chainYesNetwork of the input; payment is always USDC on Base.
tokenYesBase ERC-20 contract address or Solana mint; must match chain

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely non-obvious behavior: the endpoint is a paid x402 offer at $0.02 USDC and the call returns free payment requirements rather than executing the paid operation. That is a critical detail an agent could not derive from the annotations or schema, though what a verdict actually contains remains unexplained.

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 sentences, with the screening purpose front-loaded and no filler. The paid-offer and payment-requirements sentences are dense and slightly jarring next to the risk-screening statement, but every sentence carries information the agent needs.

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 two-parameter, read-only screening tool without an output schema, the definition covers preconditions (payment flow) well but leaves the substance thin: nothing describes what "structural risks" encompass or what the caller receives after paying. An agent knows how to call it and what it costs, but not what it will get back.

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 description coverage is 100% and the schema already documents chain, token, the address patterns, and the chain/token matching constraint via the conditional. The description adds no syntax, format, or meaning beyond that, so the baseline 3 applies.

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?

"Screen a token's structural risks" gives a specific verb plus resource, and the payment sentence scopes the tool to a risk-screening step. It does not name or distinguish itself from the sibling tools (research_pack, wallet_risk), so the agent must infer the boundary, but the core purpose is unambiguous.

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?

"before investigating a trade" implies sequencing, which is useful context for when to reach for this tool. However, there is no explicit when-not guidance and no mention of the available alternatives (research_pack, wallet_risk), so selection between 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