Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

Arbitrum is-contract check

arb_is_contract
Read-only

Check whether a 0x address on Arbitrum One is a smart contract or a plain wallet: bytecode size, whether it is an EIP-1167 minimal proxy and which implementation it points to, and whether it is a wallet that delegates to contract code (EIP-7702; delegatedTo names the code, isContract stays false). Use before sending funds or approving a spender; for a fuller risk verdict use check_counterparty. A malformed address is rejected with 400, uncharged. Example: address=0xaf88d065e77c8cC2239327C5EDb3A432268e5831. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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

Input Schema

NameRequiredDescriptionDefault
addressYes0x address

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare safety hints; the description adds the priced, charge-per-call behavior ('$0.01/call via x402 USDC or a card key', first 25 free, failed calls free) which explains why idempotentHint is false and repeats are not free. It also discloses the error path (malformed address rejected with 400, uncharged) and clarifies the non-obvious output semantics where a delegated wallet keeps isContract=false. No contradiction with readOnlyHint=true or destructiveHint=false.

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 core check and its output fields, then usage, then error and pricing details — every sentence carries information. The tail is dense (pricing, free tier, charging repeats) and could be tightened slightly, but none of it is filler.

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?

No output schema exists, and the description compensates by naming the exact fields an agent will see (bytecode size, proxy status, implementation, delegatedTo, isContract). For a single-parameter read-only tool this is complete: purpose, return shape, failure mode, cost, and the alternative are all covered.

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% and the single parameter is already documented as '0x address', so the schema carries the baseline. The description still adds value by supplying a concrete example address and stating the validation consequence for malformed input (400, uncharged), which the schema does not express.

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 whether a 0x address on Arbitrum One is a smart contract or a plain wallet') and immediately enumerates what the answer distinguishes: bytecode size, EIP-1167 minimal proxy plus implementation, and EIP-7702 delegation with the exact semantics of 'delegatedTo' versus 'isContract'. The chain is named explicitly, which cleanly separates it from the parallel *_is_contract siblings for other networks.

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 a concrete trigger ('Use before sending funds or approving a spender') and routes the agent to an alternative with a stated condition ('for a fuller risk verdict use check_counterparty'). This is explicit when-to-use plus an explicit exclusion, not implied guidance.

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.