Skip to main content
Glama

Wallet risk check

wallet_risk
Read-onlyIdempotent

Check a counterparty's known risk signals and recent USDC flows before interacting. Paid HTTP offer: $0.02 USDC. This tool returns free x402 payment requirements; it does not execute or pay for the offer.

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": {
      "chain": "<chain>",
      "address": "<address>"
    },
    "name": "wallet_risk"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainYesNetwork of the input; payment is always USDC on Base.
addressYesBase wallet or contract address

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

The annotations already declare read-only, idempotent, non-destructive, and closed-world behavior. The description adds meaningful context beyond that: it is a paid HTTP offer costing $0.02 USDC, but it returns free x402 payment requirements and does not execute or pay for the offer. This payment-flow behavior is important and not in the annotations, though details about next steps or response format are not covered.

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?

The description is three sentences and front-loads the core purpose before adding payment mechanics and a critical non-execution clarification. Every sentence adds value with no redundant or filler wording.

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?

Given the annotations and complete parameter schema, the description covers the key behavioral surprise: the tool returns free x402 payment requirements rather than executing the paid offer. It leaves some detail about the x402 flow or next steps implicit, but the essential information for an agent to call it correctly is 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%, so the input schema already documents the chain and address parameters fully. The description adds no parameter-specific meaning beyond what the schema provides, making the baseline score of 3 appropriate.

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 states a specific verb and resource: 'Check a counterparty's known risk signals and recent USDC flows.' It clearly identifies the intended pre-interaction risk check, but it does not explicitly distinguish this tool from possible siblings like token_verdict, which may also assess risk.

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?

The phrase 'before interacting' gives a clear usage context, telling the agent this is a pre-interaction check. It lacks explicit when-not-to-use guidance or named alternatives, but the timing guidance is clear and actionable.

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