Skip to main content
Glama

Base verdict

base_verdict
Read-onlyIdempotent

Simulated Base buy+sell honeypot & rug verdict (BASED/MID/COOKED/RADIOACTIVE) with round-trip cost. $0.01 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for terms, sign with your own wallet, call again with payment.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "token": "<token>"
    },
    "name": "base_verdict"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYesBase ERC20 token contract address (0x...)
paymentNosigned x402 payment payload (PAYMENT-SIGNATURE).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (read-only, idempotent, non-destructive), and the description adds context that annotations cannot convey: a $0.01 per-call charge, the accepted payment rails (USDC on Arc/Base/Solana, XNT on X1), and the mandatory two-call sign-then-pay handshake. It stops short of stating whether a failed verdict is still billed or what happens on payment rejection, which is the remaining behavioral gap.

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?

Three dense sentences, entirely front-loaded: what it returns, what it costs, how to pay. No boilerplate, no repetition of the schema, and the non-obvious payment flow is stated before an agent could get it wrong.

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?

With no output schema, the description correctly enumerates the return categories and the cost concept, so an agent knows what comes back. The payment mechanics are fully specified; only edge-case billing behavior and the magnitude/format of the round-trip cost value are left implicit.

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?

Schema description coverage is 100%, so the baseline is 3, but the description goes beyond the schema by explaining that `payment` must be a signed payload obtained from a prior unpaid call rather than something the agent can fabricate. That sequencing semantics is not inferable from the field description alone.

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

Purpose5/5

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

The description names a specific operation — a simulated Base buy+sell honeypot/rug verdict — and enumerates its discrete outputs (BASED/MID/COOKED/RADIOACTIVE) plus the round-trip cost metric. That is far more specific than siblings like contract_audit or base_token_price, so an agent can tell what it produces and roughly how it differs from a static audit or price lookup.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The procedural guidance is unusually explicit: call once without `payment` to obtain terms, sign with your own wallet, then call again with `payment`. What is missing is an explicit statement of when to prefer this over contract_audit or base_token_price, and no exclusions are given.

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