x711

x711_tx_simulate

Read-onlyIdempotent

Simulate an on-chain transaction on Base, Ethereum, Arbitrum, Optimism, Polygon, BNB Smart Chain (bnb/bsc), or opBNB L2 BEFORE broadcasting. Uses public RPC eth_call + eth_estimateGas — no wallet or API key needed. Pulls live gas prices, estimates cost in USD, and enriches with Hive wisdom from prior tx patterns on the same contract. Always simulate before calling x711_tx_broadcast. Returns: { success: bool, simulation.result, gas.estimate, gas.cost_usd, hive_wisdom, next_step }. Free tier: 3 sims/day (no API key needed).

Input Schema

TableJSON Schema

Name	Required	Description
`to`	Yes	Target contract or wallet address (0x + 40 hex chars).
`from`	No	Sender address (optional). Defaults to zero address for pure simulation.
`chain`	No	Target chain. Defaults to 'base'. Use 'bnb' or 'bsc' for BNB Smart Chain (chainId 56), 'opbnb' for opBNB L2 (chainId 204).
`value`	No	ETH value in wei (as decimal string or 0x hex). Use '0' for non-payable calls.
`calldata`	No	ABI-encoded calldata hex (0x-prefixed). Omit or use '0x' for plain ETH transfers.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`chain`	No
`success`	Yes
`gas_used`	No
`revert_reason`	No
`gas_price_gwei`	No

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare readOnly, openWorld, and idempotent hints. The description adds concrete behavioral details: uses public RPC eth_call + eth_estimateGas, pulls live gas prices, estimates USD cost, enriches with Hive wisdom, and notes the free tier limit of 3 sims/day. No contradictions with annotations.

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?

The description is concise and front-loaded with the core action, followed by technical details, return shape, and usage constraint. Every sentence adds value, though the chain list and free-tier note make it slightly longer than necessary.

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

Completeness5/5

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

Given the complexity of multi-chain simulation and the existence of an output schema, the description is highly complete. It covers purpose, usage guidance, technical approach, return fields, and constraints like the free tier. The output schema handles return value details, so no further explanation is needed.

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 each parameter (to, from, chain, value, calldata) is already well-documented. The description reinforces that calldata can be omitted for plain ETH transfers and chain aliases (bnb/bsc) exist, but does not add significant meaning beyond the schema.

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 clearly states the tool simulates an on-chain transaction before broadcasting, with a specific verb and resource. It distinguishes itself from sibling x711_tx_broadcast by explicitly saying 'Always simulate before calling x711_tx_broadcast' and listing supported chains.

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

Usage Guidelines5/5

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

Provides explicit usage guidance: 'Always simulate before calling x711_tx_broadcast.' Also notes no wallet or API key is needed and lists supported chains, giving the agent strong context for when to invoke this tool versus alternatives.

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

All x711 tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0

Disambiguation3/5

Many tools have overlapping purposes, such as multiple search tools (web_search, deep_search, data_retrieval) and multiple communication tools (agent_ping, agent_telegram, swarm_broadcast). The descriptions help differentiate, but the boundaries are not always clear.

Naming Consistency4/5

All tools consistently use the 'x711_' prefix and lowercase_with_underscores format. Submodules like agent, hive, and tx follow predictable patterns. Minor deviations (e.g., x711_ask_clerk) are rare and still descriptive.

Tool Count2/5

With 47 tools, the server is excessively large for a typical MCP service. While it aims to be a comprehensive platform, the high count makes navigation and selection cumbersome for an agent.

Completeness4/5

The tool set covers a wide range of agent needs: web access, memory, communication, on-chain transactions, code execution, and more. Minor gaps exist (e.g., no agent deletion tool), but overall it is remarkably complete for the stated purpose of an agent platform.

Resources

Need Help?