Skip to main content
Glama

Arc contract check

arc_contract_check

Before you approve, pay or trust a contract on Arc: is it really a contract, can someone change its code (EIP-1967 proxy implementation, admin and beacon slots), who is its owner(), and what token it says it is. Read live from the chain. Free, 200 calls a day.

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

Input Schema

NameRequiredDescriptionDefault
addressYes0x contract address on Arc

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: 'Read live from the chain' establishes a non-mutating, fresh-data operation, and 'Free, 200 calls a day' discloses a quota an agent must plan around. It does not say what is returned for an EOA/non-contract address or whether responses are cached, which leaves a small gap for a verification tool.

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?

One front-loaded trigger clause followed by a compact question list that maps directly to the returned signals, plus a quota note. The conversational 'is it really a contract...' framing is slightly informal but wastes no words.

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 one-parameter tool with no output schema and no annotations, the description compensates well by listing the categories of data returned (proxy slots, owner, token identity) and the freshness/cost model. Only the non-contract-address behavior and response shape remain unspecified, which is minor.

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?

There is a single required address parameter with 100% schema description coverage ('0x contract address on Arc'), so the schema already does the work. The description adds nothing about the address beyond the Arc-context already in the schema, so the baseline of 3 applies.

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?

The description names a specific verb (check) and enumerates exactly what is inspected: contract-ness, EIP-1967 proxy implementation/admin/beacon slots, owner(), and self-declared token identity. That enumeration cleanly separates it from adjacent siblings such as arc_contract_read (raw reads) and arc_trust_check (broader trust scoring).

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?

'Before you approve, pay or trust a contract' gives a concrete decision point that triggers the tool. It stops short of naming alternatives or exclusions, so an agent still has to infer when arc_contract_read or arc_trust_check would be the better call.

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