Skip to main content
Glama

walletprofile__profile

Wallet activity profile for a Base address: balance, outgoing tx count, transfer counts, counterparties, per-token flows, approval events, heuristic risk score and verdict, with a coverage block documenting every limit. Price: $0.01 per call in USDC on Base (eip155:8453), paid with x402 in params._meta["x402/payment"]. HTTP: GET https://api.firstmention.uk/s/walletprofile/profile

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

Input Schema

NameRequiredDescriptionDefault
addressYesBase address, 0x + 40 hex.
range_blocksNoHow many recent blocks to scan (default 20000, max 200000).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / address / description
      Added value: +"Base address, 0x + 40 hex."
    • addedInput schema / properties / range_blocks / description
      Added value: +"How many recent blocks to scan (default 20000, max 200000)."
    • changedInput schema / properties / range_blocks / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / required
      Added value: +[
      +  "address"
      +]
  2. Changed3 schema fields changed
    • removedInput schema / properties / address / description
      Removed value: -"0x-prefixed 20-byte Base address"
    • removedInput schema / properties / range_blocks / description
      Removed value: -"How many recent blocks to scan (2000-20000, default 20000)"
    • removedInput schema / required
      Removed value: -[
      -  "address"
      -]
  3. First observed

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses that the call is paid ($0.01 USDC on Base, eip155:8453), how payment is supplied (x402 in params._meta["x402/payment"]), the transport (GET), and the exact endpoint URL. It also promises a coverage block documenting every limit, which preempts questions about truncated history. It omits failure behavior when payment is missing, rate limits, and latency expectations.

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?

The payload of fields is front-loaded in a single dense sentence, followed by the payment and endpoint facts an agent needs before calling. Nothing is wasted, though the field enumeration is long enough that a short split into purpose/payment/transport sentences would read better.

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 paid GET endpoint with no output schema, the description covers cost, payment channel, transport, endpoint, and the shape of the response including a self-documenting coverage block. Remaining gaps — behavior on unpaid or invalid requests and sibling differentiation — are meaningful but secondary to correctness of invocation.

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 two declared parameters are already documented, which sets a baseline of 3. The description goes beyond that by introducing a payment parameter injected via params._meta["x402/payment"] that does not appear in the input schema at all — critical meaning the agent would otherwise miss.

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?

Names a specific resource and scope ("Wallet activity profile for a Base address") and enumerates exactly what it contains: balance, outgoing tx count, counterparties, per-token flows, approvals, risk score and verdict. An agent knows precisely what it gets back. It stops short of distinguishing itself from close siblings such as walletprofile__hygiene or walletprofile__sanctions.

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

Usage Guidelines2/5

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

There is no when-to-use guidance and no mention of alternatives, despite several overlapping siblings (walletprofile__hygiene, walletprofile__monitor, walletprofile__sanctions, token_dd__wallet). The only implied usage cue is the enumerated contents. The agent must infer selection entirely from sibling names.

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