Skip to main content
Glama

Address identify

address_identify
Read-onlyIdempotent

Identify an EVM 0x address (EIP-55 checksum, EOA vs contract/proxy/ERC20 across 8 EVM chains: Eth/Base/Arb/OP/Polygon/BNB/Arc/Robinhood) or base58 32-byte Solana/X1 key size. $0.002 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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

Input Schema

NameRequiredDescriptionDefault
addressYes0x EVM address or base58 key string
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

A4.4/5.0
Behavior4/5

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

Beyond the annotations (readOnly, idempotent, open-world, non-destructive), it discloses the cost ($0.002 per call), the accepted payment rails (USDC on Arc/Base/Solana, XNT on X1), the x402 two-step handshake, and the exact chain coverage. It does not describe the response shape, which matters since there is no output schema. Note a mild tension: the description says 'the purchase completes inside this tool call', which is a financial side effect under a readOnlyHint=true annotation — worth flagging to callers but not a direct factual contradiction.

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 sentences, each carrying distinct load: what is identified, what it costs and on which rails, and how to invoke it. The chain list is compressed into one parenthetical rather than prose, and the payment workflow is placed last where the agent needs it at call time.

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 must convey what comes back, and it does so at a category level (checksum status, account type, per-chain results, key size) plus the payment handshake. What is missing is the concrete response structure or error behavior when an address is malformed, which is a modest gap for a two-parameter lookup 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?

Schema coverage is 100%, so both parameters are already documented, and the baseline would be 3. The description earns extra credit by explaining the semantics the schema cannot: `payment` is not just 'a signed x402 payment' but the second half of a required two-call negotiation, and the first call's purpose (retrieving terms) is stated explicitly.

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 ('Identify') and resource ('EVM 0x address' / 'base58 32-byte Solana/X1 key'), then enumerates exactly what is determined: EIP-55 checksum validity, EOA vs contract/proxy/ERC20, across eight named chains. That is far more specific than siblings like evm_code or wallet_investigate, so an agent can route without opening the schema.

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 description gives explicit invocation sequencing: call once without `payment` to receive terms, sign with your own wallet, call again with `payment` to complete. That is unusually actionable. It stops short of saying when to prefer this over sibling tools such as wallet_investigate or evm_code, so it is clear context but not full alternative routing.

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