Skip to main content
Glama

Wallet alert

wallet_alert

Watch one Base or Arc wallet for 24 hours ($0.005 on Base) and alert on USDC or gas balance moves. Pass wallet= + chain=base|arc, or id=. $0.005 per call over x402 (USDC on Base only). Call once without payment for the terms, sign them with your own wallet, call again with payment.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "wallet_alert"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNo32-hex watch id to read alerts
chainNobase or arc (default base)
walletNo0x address to watch
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/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 well: it discloses the 24-hour watch duration, the $0.005 per-call price, the x402/USDC-on-Base payment rail, and that a first call returns terms requiring a self-signed payment. The notable gap is alert delivery — it never says how alerts surface or that they are retrieved via id=, which matters for a tool whose whole output is an alert.

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?

Three sentences, front-loaded with purpose and scope before the pricing and payment mechanics. The price appears twice ($0.005 on Base, then $0.005 per call over x402), a small redundancy, but otherwise every sentence carries information an agent needs before calling.

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 4-parameter tool with no annotations and no output schema, the definition covers purpose, cost, watch window, both input modes, and the payment handshake. The remaining hole is the alert lifecycle — how results are read back and whether a watch can be reused or extended — which the description only hints at through id=.

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%, so the schema already documents all four parameters including the base64 PAYMENT-SIGNATURE payload. The description reinforces the wallet+chain pairing and the id-read mode, but adds little syntax or format detail beyond what the schema states, so the baseline 3 applies.

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 gives a specific verb and resource: watch one Base or Arc wallet for 24 hours and alert on USDC or gas balance moves. Scope is narrowed precisely (single wallet, two chains, two balance types), which implicitly separates it from broader siblings like wallet_investigate or rug_alert, though no sibling is named explicitly.

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?

It explains the two invocation modes (wallet= + chain=, or id=) and the two-step payment flow, which is procedural guidance rather than when-to-use guidance. It never says when to pick this over alternatives such as rug_alert or arc_wallet_value, leaving the agent to infer selection.

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