Skip to main content
Glama

wallet_safety

Read-onlyIdempotent

Comprehensive wallet safety check: scans approvals, analyzes recent transaction activity for suspicious patterns, and assesses target contract risk. Returns composite risk score (0-100), risk level, action items, and related service suggestions. Supports EVM chains and Solana. Free over MCP for 10 calls per day; beyond that the tool returns the pay-per-call x402 endpoint and its price.

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": {
      "walletAddress": "<walletAddress>"
    },
    "name": "wallet_safety"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoBlockchain network (includes Solana support)ethereum
depthNoAnalysis depth: quick (approvals only), standard (approvals + activity), deep (extended history + all patterns)standard
walletAddressYesWallet address to check (0x-prefixed for EVM, base58 for Solana)
targetContractNoOptional target contract address to assess before interaction

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Beyond the annotations (which only establish read-only, idempotent, open-world behaviour), the description discloses the concrete return payload (composite risk score 0-100, risk level, action items, related service suggestions), the supported chain families, and an unusual operational trait: a free tier of 10 calls/day after which the tool surfaces a pay-per-call x402 endpoint and price. That quota and cost-fallback behaviour is exactly the kind of context annotations cannot carry.

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 tight sentences, front-loaded with what is scanned, then what is returned, then the operational constraints. No sentence is redundant and the pricing caveat is placed after the core capability rather than padding the opening.

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 correctly takes on the burden of describing the return values and does so at a summary level (score, level, action items, suggestions) plus the quota fallback. It stops short of indicating the response structure or how the composite score is composed, which would help an agent interpret results, but the essentials for calling it correctly are present.

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 description coverage is 100% and the depth enum already spells out quick/standard/deep semantics, so the schema does the heavy lifting. The description restates chain coverage (EVM plus Solana) and ties targetContract to pre-interaction risk assessment, which is marginal added meaning rather than new semantics.

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 and breaks the tool into its three component analyses (approvals, transaction activity patterns, target contract risk) plus the composite output. This scope implicitly separates it from narrower siblings such as approval_scan and address_check, but it never names an alternative, so an agent must infer the boundary rather than read it.

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 'comprehensive' and by the parenthetical about assessing a target contract before interaction, which hints at a pre-transaction safety gate. However, there is no explicit statement of when to pick this over approval_scan, token_risk_metrics, or risk_batch, and no exclusions or prerequisites are stated.

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.