Skip to main content
Glama

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

Polygon is-contract check

polygon_is_contract
Read-only

Check whether a 0x address on Polygon PoS 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=0x3c499c542cEF5E3811e1192ce70d8cC03d5c3359. 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": "polygon_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 already declare readOnlyHint, destructiveHint=false and openWorldHint, but the description adds substantial context beyond them: malformed addresses are rejected with 400 uncharged, pricing is $0.01/call with first 25 free, failed calls are free, and repeats are billed — which explains the non-obvious idempotentHint=false. It also states 'reads or computes only and changes nothing', consistent with the annotations rather than contradicting them.

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 purpose and the return semantics before commercial detail, with zero filler sentences. It is dense and slightly run-on, packing pricing, example, and error behavior into one paragraph, but each clause carries actionable information.

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 one-parameter, no-output-schema tool, the description covers the expected return fields (bytecode size, proxy status, delegatedTo, isContract), the error case, and the cost model. An agent has everything needed to call it correctly and interpret the result without opening anything else.

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% for the single 'address' parameter, so the baseline is 3; the description still adds value by supplying a concrete example address and by documenting the failure mode for a malformed address (400, uncharged). No further syntax is needed for a one-parameter tool.

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+resource+chain ('Check whether a 0x address on Polygon PoS is a smart contract or a plain wallet') and enumerates exactly what the response distinguishes: bytecode size, EIP-1167 minimal proxy status plus implementation, and EIP-7702 delegation. It even clarifies the edge case semantics (delegatedTo names the code, isContract stays false), which an agent can use to tell this apart from polygon_proxy and the other *_is_contract siblings.

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 trigger ('Use before sending funds or approving a spender') and routes the agent to the right alternative for a different need ('for a fuller risk verdict use check_counterparty'). The conditional logic for choosing between the two tools is stated rather than inferred.

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.