Skip to main content
Glama

token_verdict_lite

Read-onlyIdempotent

FREE lite Base token verdict for a token contract address. Runs the same 10 checks as token_verdict but returns top-line results only: the GO / HOLD / BLOCK decision, the one-line verdict, 0-100 score, A-F grade, risk level, and the top 3 flag titles — detail is capped (no per-check evidence, no market block). Use this to triage whether a token deserves the full token_verdict report, or call token_verdict directly for the complete evidence-backed scan.

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": {
      "address": "<address>"
    },
    "name": "token_verdict_lite"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesBase token contract address (0x-prefixed, 40 hex chars), e.g. 0x4ed4E862860beD51a9570b96d89aF5E1B0Efefed

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), and the description adds the details that matter operationally: it runs the same 10 checks as the full tool, is free, and truncates output (no per-check evidence, no market block). Disclosing the output truncation is exactly the kind of context annotations cannot carry.

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 sentences, front-loaded with the identity of the tool, followed by the return payload and then the routing decision. Dense but every clause carries information; no filler or repetition of the schema.

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?

With no output schema, the description compensates by enumerating the returned fields (GO/HOLD/BLOCK, one-line verdict, score, grade, risk level, top 3 flag titles) and what is omitted. For a one-parameter read tool, an agent has everything needed to call it and interpret the result.

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 coverage is 100% with a single required parameter that already documents the 0x-prefixed 40-hex format and gives an example. The description reinforces that this is a Base-chain contract address but adds no syntax or format detail beyond the schema, so the baseline of 3 applies.

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?

States a specific verb+resource combination ("lite Base token verdict for a token contract address") and immediately scopes it as the lightweight counterpart to token_verdict. An agent can tell exactly what it gets back and how it differs from the sibling without opening either schema.

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

Usage Guidelines5/5

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

Gives an explicit decision rule: use this to triage whether a token deserves the full report, or call token_verdict directly when complete evidence is needed. Both branches of the choice are named, so nothing 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.