Skip to main content
Glama
Sign In

VerifyLite

by io.github.SecondShotAI
OverviewDiscussionsAdmin

Token safety check on Base: can the owner mint, pause, blacklist, change taxes, or upgrade?

token_safety_check
Read-only

Risk check for an ERC-20 token on Base before buying, accepting, or holding it: reads the contract and its proxy implementation for owner powers (minting, pausing, blacklisting wallets, changing buy/sell taxes, trade limits, trading switches, burning others' tokens, upgrades), checks whether ownership was renounced and how much supply the owner holds. Returns a verdict, 0-100 risk score, and plain-language flags. Read-only. Not charged for invalid addresses or non-tokens. Paid via x402; see list_prices.

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_safety_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesToken contract 0x address on Base.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the readOnlyHint annotation: discloses proxy-implementation reading, renouncement/owner-supply checks, the return shape (verdict, 0-100 score, flags), billing behavior ('not charged for invalid addresses or non-tokens'), and the x402 payment path. No contradiction with readOnlyHint=true.

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?

One dense sentence front-loads purpose and scope, followed by return shape, read-only, and billing notes. Every clause carries information, though the parenthetical power list is long enough to slow scanning slightly.

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?

No output schema exists, but the description compensates by naming the return values (verdict, 0-100 score, plain-language flags) and the billing edge cases. An agent has everything needed to decide 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?

With schema coverage at 100% for the single 'address' parameter, the schema already carries the semantics. The description only reinforces the Base chain constraint and adds no format or validation detail beyond that, so baseline 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 and resource ('Risk check for an ERC-20 token on Base') and enumerates exactly what powers it inspects (mint, pause, blacklist, taxes, upgrades). This cleanly separates it from generic siblings like chain_token or chain_contract, which would not return a risk verdict.

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?

Explicitly frames the decision context: 'before buying, accepting, or holding it.' It doesn't name an alternative sibling to use instead, so it stops short of a 5, but the when-to-use condition is unambiguous.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All VerifyLite toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources