Skip to main content
Glama

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

Base is-contract check

base_is_contract
Read-only

Check whether a 0x address on Base 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=0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913. 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": "base_is_contract"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYes0x address

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover read-only/destructive status, but the description adds real behavioral context: malformed addresses return 400 uncharged, failed calls are free, and each successful call is billed so repeats cost money — which explains the idempotentHint=false. It also discloses the EIP-7702 edge case where delegatedTo is set while isContract stays false, a nuance an agent could otherwise misread. Pricing detail is present but the per-call cost mechanics are stated without a full billing-flow explanation.

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-loads the core check and the returned fields, then usage guidance, then pricing. Dense but nearly every clause carries information; the pricing/credits sentence is the heaviest and slightly crowds an otherwise tight definition.

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 no output schema, the description compensates by naming the returned signals (bytecode size, proxy status, implementation, delegatedTo, isContract) and the error behavior. For a one-parameter read tool this covers everything needed to invoke and interpret it correctly.

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, so the baseline is 3; the description adds a concrete example address and the validation contract (malformed input rejected with 400, uncharged), which meaningfully extends what the schema says.

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 — checking whether a 0x address on Base is a contract or wallet — and enumerates the exact facts returned (bytecode size, EIP-1167 proxy + implementation, EIP-7702 delegation). The Base chain scoping plus the pointer to check_counterparty separates it cleanly from the sibling *_is_contract tools.

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 an explicit when-to-use ('before sending funds or approving a spender') and names the alternative with the condition that selects it ('for a fuller risk verdict use check_counterparty'). Nothing about tool selection is left to inference.

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.