Straelo Relay

Chain Contract Call

chain_contract_call

Read-only

Execute a read-only EVM smart contract call on Ethereum or Base and return the normalized result without managing an RPC provider.

Input Schema

TableJSON Schema

Name	Required	Description
`data`	Yes	Read-only hexadecimal ABI calldata.
`chain`	Yes	EVM network for the read-only call.
`contract_address`	Yes	Target EVM contract address.

Output Schema

TableJSON Schema

Name	Required	Description
`chain`	Yes	Selected EVM network.
`result`	Yes	Hexadecimal eth_call result.
`provider`	Yes	RPC provider identifier.
`latency_ms`	Yes	Observed provider-call latency in milliseconds.
`contract_address`	Yes	Called contract address.

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedSep 28, 2026

addedInput schema / properties / chain / description

Added value: +"EVM network for the read-only call."

addedInput schema / properties / chain / title
```
Added value: +"Chain"
```
addedInput schema / properties / contract_address / description
```
Added value: +"Target EVM contract address."
```
addedInput schema / properties / contract_address / title
```
Added value: +"Contract Address"
```

changedInput schema / properties / data / description

Previous value: -"Hexadecimal EVM calldata."New value: +"Read-only hexadecimal ABI calldata."

addedInput schema / properties / data / title
```
Added value: +"Data"
```
addedInput schema / title
```
Added value: +"handlerArguments"
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "chain": {
+      "description": "Selected EVM network.",
+      "type": "string"
+    },
+    "contract_address": {
+      "description": "Called contract address.",
+      "type": "string"
+    },
+    "latency_ms": {
+      "description": "Observed provider-call latency in milliseconds.",
+      "type": "integer"
+    },
+    "provider": {
+      "description": "RPC provider identifier.",
+      "type": "string"
+    },
+    "result": {
+      "description": "Hexadecimal eth_call result.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "chain",
+    "contract_address",
+    "result",
+    "provider",
+    "latency_ms"
+  ],
+  "title": "ChainContractCallOutput",
+  "type": "object"
+}

First observedSep 27, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint false, and destructiveHint false, so the safety profile is covered. The description adds that the result is normalized and that no RPC provider is needed, but says nothing about rate limits, revert/error behavior, or latency.

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?

One tightly written sentence with the verb, resource, scope, and benefit front-loaded. Zero filler.

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?

With a full input schema, complete annotations, and an output schema, the description need only frame the operation, which it does. It omits any note on failure modes or output shape beyond 'normalized result', a minor gap for an open-world RPC-backed call.

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% and each of the three parameters is documented in the schema, so baseline 3 applies. The description only echoes the chain scope ('Ethereum or Base'), which the enum already conveys, adding no new syntax or format detail.

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 (execute a read-only call), resource (EVM smart contract), and scope (Ethereum or Base), plus the value proposition of not managing an RPC provider. No sibling tool covers this capability, so the agent can distinguish it easily.

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

Usage Guidelines3/5

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

The 'read-only' qualifier implicitly excludes state-changing calls, which is useful context, but there is no explicit when-to-use/when-not guidance or named alternative. Usage is only implied from the tool's nature.

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

All Straelo Relay tools Inspect

Try in Browser

Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?