Skip to main content
Glama
devx-address-poisoning-check

devx-address-poisoning-check

How to buy the on-chain poisoning check

onchain_check_info
Read-onlyIdempotent

Retrieve the endpoint, price, and payment method for a paid on-chain scan that detects address-poisoning transfers in a wallet’s Ethereum or Base history and returns a verdict and evidence.

Instructions

Returns the endpoint, price and payment method of the optional paid hosted check. It does not call the API and does not pay or sign anything. The paid check reads the sending wallet's real transfer history on Ethereum and Base (optionally Avalanche), finds poisoning transfers (zero-value, dust or fake-token transfers from lookalike addresses) and returns a verdict ok | caution | danger, the address you probably meant, and evidence transaction hashes. It costs 0.005 USDC on Base via x402. Use it when you have no trusted address list to pass to check_recipient_lookalike, or when check_recipient_lookalike returns unknown for a recipient copied from transaction history. Returns: method, url_template, price_usdc, network, asset, protocol, chains, settles and docs.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
docsYes
assetYes
chainsYes
methodYes
networkYes
settlesYes
protocolYes
price_usdcYes
url_templateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": false,
      +  "properties": {
      +    "asset": {
      +      "type": "string"
      +    },
      +    "chains": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "docs": {
      +      "type": "string"
      +    },
      +    "method": {
      +      "type": "string"
      +    },
      +    "network": {
      +      "type": "string"
      +    },
      +    "price_usdc": {
      +      "type": "number"
      +    },
      +    "protocol": {
      +      "type": "string"
      +    },
      +    "settles": {
      +      "type": "string"
      +    },
      +    "url_template": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "method",
      +    "url_template",
      +    "price_usdc",
      +    "network",
      +    "asset",
      +    "protocol",
      +    "chains",
      +    "settles",
      +    "docs"
      +  ],
      +  "type": "object"
      +}
  2. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations (read-only, non-destructive, idempotent), the description clarifies that this tool does not call the API and does not pay or sign anything. It also discloses the paid check's behavior, verdict values, cost (0.005 USDC on Base via x402), and evidence returned, giving the agent a complete picture of side effects and external dependencies.

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 description is front-loaded with the core purpose and each sentence carries useful information about behavior, cost, and usage. The final sentence listing return fields is slightly redundant given the output schema, but overall it is tight and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With zero parameters, full annotations, and an output schema, the description covers everything an agent needs: what the tool returns, what it does not do, the paid check's cost and behavior, and when to use it instead of the sibling tool.

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?

The tool has zero parameters, so parameter semantics are not applicable. The description does not need to explain parameters, and the baseline of 4 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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: it returns the endpoint, price, and payment method of the optional paid hosted check. It also explicitly distinguishes this tool from the sibling by naming check_recipient_lookalike and explaining the paid check's purpose.

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

Usage Guidelines5/5

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

It gives explicit when-to-use conditions: 'Use it when you have no trusted address list to pass to check_recipient_lookalike, or when check_recipient_lookalike returns unknown for a recipient copied from transaction history.' This names both the trigger and the alternative tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools