Skip to main content
Glama

EVM & Solana Chain Reads (Tanod)

check_contract_before_interaction

Read-onlyIdempotent

txpeek: Check an address for risk right before you send a transaction to it, approve it, or buy its token (Base or Ethereum). For a full scan of verified source use scan_contract_address; for a token's sellability use check_token_honeypot. Returns verdict (low | caution | high | unknown), risk_score 0-100 and plain-language reasons, e.g. upgradeable by a single key, unverified source, mint/blacklist/fee functions, SELFDESTRUCT or DELEGATECALL, an EOA where a contract was expected. Price: USD 0.005. Free: 3 scans or 30 txpeek checks per IP per UTC day. Typically under 1 s (p95 about 1 s), at most about 4 s; results are cached for 10 min. If the chain cannot be read the call fails and is not charged. Heuristic, not an audit: the buy/sell (honeypot) simulation of ERC-20 tokens sees one trade now, there is no oracle analysis, and a low verdict is not a clearance. Docs: https://tanod.dev/learn/contract-address-risk-check-api.html

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>",
      "chain": "<chain>"
    },
    "name": "check_contract_before_interaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainYesChain the contract is deployed on.
addressYesAddress you are about to interact with (0x + 40 hex).

Output Schema

NameRequiredDescriptionDefault
okNo
chainNo
errorNoOnly on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object.
schemaNo
addressNo
reasonsNo
verdictNo
disclaimerNo
latency_msNo
risk_scoreNo
checked_at_blockNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedInput schema / properties / address / title
      Removed value: -"Address"
    • removedInput schema / properties / chain / title
      Removed value: -"Chain"
    • removedInput schema / title
      Removed value: -"check_contract_before_interactionArguments"
    • removedOutput schema / properties / reasons / items
      Removed value: -{
      -  "properties": {
      -    "code": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "message": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "points": {
      -      "type": [
      -        "integer",
      -        "null"
      -      ]
      -    },
      -    "severity": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    }
      -  },
      -  "type": [
      -    "object",
      -    "null"
      -  ]
      -}
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "address": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "chain": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "checked_at_block": {
      +      "type": [
      +        "integer",
      +        "null"
      +      ]
      +    },
      +    "disclaimer": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "error": {
      +      "description": "Only on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object."
      +    },
      +    "latency_ms": {
      +      "type": [
      +        "integer",
      +        "null"
      +      ]
      +    },
      +    "ok": {
      +      "type": [
      +        "boolean",
      +        "null"
      +      ]
      +    },
      +    "reasons": {
      +      "items": {
      +        "properties": {
      +          "code": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "message": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "points": {
      +            "type": [
      +              "integer",
      +              "null"
      +            ]
      +          },
      +          "severity": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          }
      +        },
      +        "type": [
      +          "object",
      +          "null"
      +        ]
      +      },
      +      "type": [
      +        "array",
      +        "null"
      +      ]
      +    },
      +    "risk_score": {
      +      "maximum": 100,
      +      "minimum": 0,
      +      "type": [
      +        "integer",
      +        "null"
      +      ]
      +    },
      +    "schema": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "verdict": {
      +      "enum": [
      +        "low",
      +        "caution",
      +        "high",
      +        "unknown",
      +        null
      +      ],
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    }
      +  },
      +  "type": "object"
      +}
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Far beyond the readOnly/idempotent/non-destructive annotations, it discloses price (USD 0.005), free-tier limits (3 scans or 30 checks per IP per UTC day), latency expectations (under 1 s typical, ~4 s max), 10-minute result caching, and that a failed chain read is not charged. It also enumerates the risk signals surfaced (upgradeable by a single key, unverified source, mint/blacklist/fee functions, SELFDESTRUCT/DELEGATECALL, EOA-where-contract-expected) and the coverage limits of the honeypot simulation. No contradiction with annotations — this is a read-only analysis call.

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?

Front-loaded with the action and trigger, then alternatives, then results, then commercial/operational facts. Dense but nearly every clause earns its place; pricing, rate limits, and the docs URL could arguably be trimmed or split out, which keeps it just short of a 5.

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?

For a two-parameter read-only scan, it covers purpose, alternatives, return shape (verdict, risk_score, plain-language reasons), cost, limits, latency, caching, and failure behavior, plus an explicit statement of methodological limits. Even though an output schema exists, the description still clarifies the verdict/score semantics an agent needs to act on.

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 both address and chain are fully documented in the schema with a pattern and an enum. The description adds only the chain set ("Base or Ethereum") and the intent behind the address ("the address you are about to interact with"), which the schema already conveys. Baseline 3 is appropriate.

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?

States a specific verb and resource ("Check an address for risk") plus the triggering moments (before sending a transaction, approving, or buying a token) and supported chains (Base or Ethereum). It explicitly names the sibling tools it is not — scan_contract_address for full source scans and check_token_honeypot for sellability — so an agent can distinguish it without opening a schema.

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?

Gives explicit when-to-use framing (right before interacting with an address) and routes to named alternatives with the condition that selects them (full verified-source scan → scan_contract_address; token sellability → check_token_honeypot). It also states a when-not caveat: "Heuristic, not an audit... a low verdict is not a clearance."

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.