Skip to main content
Glama

Arc contract read

arc_contract_read

Contract read on Arc: one view call on any contract, decoded, with block and time (owner, paused, allowance, balance...). Only view/pure functions; a revert or non-contract is refused before payment. $0.001 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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>",
      "fn": "<fn>"
    },
    "name": "arc_contract_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
fnYesfunction signature, e.g. function balanceOf(address) view returns (uint256)
argsNooptional: JSON array of arguments
blockNooptional: a past block number
addressYescontract address (0x...)
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden, and it does well: it discloses the payment model ($0.001 per call via x402 in USDC on Arc/Base/Solana or XNT on X1), that reverts and non-contract addresses are refused before payment, and that only view/pure functions are permitted. Remaining unknowns such as rate limits or whether a failed call is charged in any edge case are minor.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences: capability and scope first, safety/refusal behavior second, pricing and invocation protocol last. The parenthetical example list is compact and every clause carries information an agent needs.

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 paid, two-phase call with no output schema, the description supplies what is needed: decoded return with block and time, function-type restriction, failure handling, cost, currency rails, and the payment handshake. It stops short of describing the exact shape of the terms returned by the unpaid call, which would help the agent parse the first response.

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%, so the baseline is 3; the description adds meaning beyond it by explaining the `payment` parameter's role in the two-call handshake (first call returns terms, second call completes the purchase inside the tool invocation). It adds little on `fn`/`args`/`block` beyond what the schema already documents.

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?

Opens with a specific verb and resource ('one view call on any contract, decoded, with block and time') and the examples (owner, paused, allowance, balance) make the payload concrete. It is clearly distinguishable from the sibling checks such as arc_contract_check or arc_allowance, which do not perform arbitrary contract calls.

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?

Gives an explicit two-step invocation protocol: call once without `payment` to get terms, sign with your own wallet, call again with `payment`. It also scopes the tool to view/pure functions only. It does not name which sibling to prefer for related queries (e.g. arc_contract_check vs arc_allowance), which is the only gap.

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