Skip to main content
Glama

Rokha

by ai.rokha
OverviewDiscussionsAdmin

Read contract or account state

singularityagent__read_contract
Read-only

Call a view function on an EVM contract (supply abi in human-readable form plus method), or read parsed account data on Solana. Pass atBlock to call against a past block. Never sends a transaction.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
abiNoHuman-readable ABI entry, e.g. "function balanceOf(address) view returns (uint256)".
argsNoArguments for the call, in order.
chainYesChain id or alias.
methodNoEVM function name, e.g. "balanceOf".
addressYesContract address (EVM) or account address (Solana).
atBlockNoRead state as of this block height instead of now. Supported on EVM (needs an archive endpoint) and Cosmos (needs an archive LCD). Solana and UTXO chains reject it outright rather than answering with current state, so a result carrying `atBlock` is always genuinely historical.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / additionalProperties
      Previous value: -trueNew value: +false
    • addedInput schema / properties
      Added value: +{
+  "abi": {
+    "description": "Human-readable ABI entry, e.g. \"function balanceOf(address) view returns (uint256)\".",
+    "type": "string"
+  },
+  "address": {
+    "description": "Contract address (EVM) or account address (Solana).",
+    "type": "string"
+  },
+  "args": {
+    "description": "Arguments for the call, in order.",
+    "items": {},
+    "type": "array"
+  },
+  "atBlock": {
+    "description": "Read state as of this block height instead of now. Supported on EVM (needs an archive endpoint) and Cosmos (needs an archive LCD). Solana and UTXO chains reject it outright rather than answering with current state, so a result carrying `atBlock` is always genuinely historical.",
+    "type": [
+      "string",
+      "number"
+    ]
+  },
+  "chain": {
+    "description": "Chain id or alias.",
+    "type": "string"
+  },
+  "method": {
+    "description": "EVM function name, e.g. \"balanceOf\".",
+    "type": "string"
+  }
+}
    • addedInput schema / required
      Added value: +[
+  "chain",
+  "address"
+]
  2. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description reinforces this with 'Never sends a transaction' and 'Call a view function.' It adds the useful behavioral nuance that atBlock enables past-block reads, which is more specific than the annotation alone. It does not cover auth, rate limits, or return format, but those are not critical for a read-only tool.

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 sentences with no filler. The main action is front-loaded, the atBlock usage is stated compactly, and the safety guarantee closes it. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers EVM and Solana usage and the read-only guarantee, but it omits Cosmos support that appears in the atBlock schema description. It also does not describe the return shape, though no output schema exists. For a multi-chain read tool, this is a noticeable gap.

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 description coverage is 100%, so the baseline is 3. The description adds minor value by explaining that abi should be supplied in human-readable form alongside method, and by clarifying atBlock's purpose, but these points are already present in the schema descriptions. No significant new parameter semantics are introduced.

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 and resource: 'Call a view function on an EVM contract' or 'read parsed account data on Solana.' It also distinguishes itself from transaction-sending tools by stating 'Never sends a transaction,' making its read-only role unambiguous among siblings like singularityagent__transaction.

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?

The description gives clear context for when to use the tool: for EVM view-function calls or Solana account reads, with atBlock for historical state. It does not explicitly name alternative tools or list exclusions beyond 'Never sends a transaction,' so it falls short of fully explicit when-not-to-use guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Rokha toolsInspect
Try in Browser
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources