Skip to main content
Glama

Base Agent Due-Diligence Kit

Wallet X-Ray teaser (free)

wallet_xray_peek
Read-onlyIdempotent

FREE. Free teaser of Wallet X-Ray for a Base address: type, age bucket and headline signal. Full report: wallet_xray.

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

Input Schema

NameRequiredDescriptionDefault
addressYesBase address

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the description's added value is the cost dimension: it is free and deliberately truncated to three fields. That cost/scope trade-off is genuinely useful and not derivable from the annotations. Minor gap: no note on whether the free teaser is rate-limited or cached.

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 short fragments, front-loaded with 'FREE.', then scope, then the alternative. Every element earns its place with zero filler.

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 usefully previews the three returned fields, which is the key thing an agent needs to decide between this and the full report. It is slightly incomplete about what a 'headline signal' contains and any free-tier limits, but adequate for a one-parameter read tool.

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?

One parameter with 100% schema description coverage including a regex pattern, so the schema does the heavy lifting. The description only restates that the address is a Base address, adding chain identity but no format or validation detail beyond the pattern.

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 it is a teaser of Wallet X-Ray for a Base address and enumerates the three fields returned (type, age bucket, headline signal), which distinguishes it from the sibling wallet_xray full report. The content of 'type' and 'headline signal' is left somewhat vague, so the shape of the purpose is clearer than the substance.

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 names the alternative ('Full report: wallet_xray') and gives the selection criterion implicitly via 'FREE' / 'teaser' versus full report. It does not spell out when a cheap teaser is insufficient (e.g., needing transaction history), but the routing guidance is clear enough to act on.

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