Skip to main content
Glama

Veriql token check

veriql_token

Check a token contract for honeypot, punishing-tax, mintable-supply, hidden-owner and proxy risks, returning plain-English flags across EVM chains and Tron.

Instructions

Check a token contract for honeypot, punishing taxes, mintable supply, hidden owner and proxy risks, each surfaced as a plain-English flag. EVM chains + Tron.

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": "veriql_token"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesToken contract address
chainIdNoChain id or key (e.g. 1, base, tron); defaults to Ethereum

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.1

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does well on output semantics by saying each risk is 'surfaced as a plain-English flag' and it implicitly frames the tool as a read-only check. It says nothing about latency, cost, rate limits, behavior on unverified/unavailable contracts, or how flags are represented (boolean, severity, text), which matters with zero annotation coverage.

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 short sentences with no filler; the risk enumeration is front-loaded and immediately actionable, and the chain scope closes the definition. Every clause adds information.

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 tool with no annotations and no output schema, the description covers what is checked and roughly how results are expressed. It is thin on return structure — no mention of an aggregate verdict, flag severity, or handling of unverified contracts — leaving the agent to discover result shape at call time.

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% for both parameters, so the schema already documents 'address' and 'chainId' including the Ethereum default. The description's only added meaning is the chain scope ('EVM chains + Tron'), which usefully bounds the valid chainId values. Baseline 3 fits.

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?

The description names a specific verb and resource ('Check a token contract') and enumerates exactly what is inspected: honeypot, punishing taxes, mintable supply, hidden owner, proxy risks. It also states chain coverage ('EVM chains + Tron'), which narrows the domain. It stops short of naming which sibling to use instead (e.g. veriql_scan or veriql_preflight), so an agent must infer the split.

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?

Usage is implied by the risk list — you call this when you want a safety screening of a token contract — and the chain scope acts as a soft boundary. However, there is no explicit when-to-use vs. when-to-use-alternative guidance against siblings such as veriql_scan, veriql_preflight or veriql_batch_screen, and no stated preconditions or exclusions.

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