Skip to main content
Glama

zato crypto data

Contract info: verified source?, name, compiler, creator and creation tx, proxy hint

contract_info
Read-only

Provenance of a contract: verified source?, name, compiler, creator, creation tx (Ethereum, zkSync, Celo). Price: $0.002 USDC per call (x402, Base).

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

Input Schema

NameRequiredDescriptionDefault
addressYescontract address
networkNoethereum (default), zksync or celo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely new context by stating supported chains (Ethereum, zkSync, Celo) and a per-call price of $0.002 USDC via x402 on Base, which is important behavioral/cost information an agent cannot get from structured fields.

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?

Compact, front-loaded with the returned fields before secondary details like chains and pricing. The parenthetical network list duplicates schema content and could be trimmed, but overall there is little waste.

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?

For a simple two-parameter read tool with no output schema, the description covers what is returned, which chains are supported, and the cost of a call. Minor gaps remain: behavior when a contract is unverified or not found, and any address-format expectations.

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 coverage is 100%, so both 'address' and 'network' are already documented with examples and the default. The description's network list restates what the schema conveys, adding no format or validation detail beyond it, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a concrete resource (contract provenance) and enumerates the exact fields returned: verified source flag, name, compiler, creator, and creation transaction. That field list implicitly separates it from siblings like token_risk or tx, though no alternative is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance, and no named alternative such as token_risk or approvals_report. The only usage signal is the implicit 'look up a contract's provenance' framing from the field list.

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