Skip to main content
Glama

Veriql wallet scan

veriql_scan

Scan a public EVM wallet for risky token approvals across Ethereum, BNB Chain, Polygon, Arbitrum, and Base; returns a 0–100 security score, itemized drivers, flagged approvals, and USD value-at-risk.

Instructions

Scan a public wallet address for risky token approvals across 5 EVM chains (Ethereum, BNB Chain, Polygon, Arbitrum, Base). Returns a 0-100 Security Score with itemised drivers, every risky approval, and a best-effort USD value-at-risk.

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

Input Schema

NameRequiredDescriptionDefault
addressYesPublic EVM address, 0x…

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.1

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does reasonably well: it discloses the chain coverage, the returned artifact (0-100 score, itemised drivers, every risky approval, USD value-at-risk) and flags the valuation as best-effort. It never explicitly says the operation is read-only, requires no signing or key material, or whether it consumes quota.

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 dense sentences with zero filler; the scope and chain list come first, then the return payload. Nothing is repeated from the title or schema.

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?

For a one-parameter read tool without an output schema, the description does the important work of enumerating the response contents so an agent knows what it will get. The remaining gap is safety framing, since with no annotations the description should state explicitly that this is a read-only scan that moves no funds.

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 coverage is 100%, so the baseline is 3, and the description adds meaning by specifying the address must be a public wallet address on EVM chains, framing the input as an identifier rather than a key or contract. It does not add format or chain-scoping syntax beyond that.

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?

States a specific verb and resource ("Scan a public wallet address for risky token approvals") plus the chains covered and what comes back. It is easy to tell apart from siblings like veriql_signature or veriql_send, but it never explicitly contrasts itself with veriql_batch_screen, which sounds adjacent.

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: call this to vet a single wallet's approval exposure before interacting with it. There is no explicit when-not guidance, no mention of when to prefer batch screening across many addresses, and no stated prerequisites.

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