x711 — Universal Agent Gas Station

x711_tx_broadcast

Destructive

Relay a pre-signed EVM transaction to Base, Ethereum, Arbitrum, Optimism, Polygon, BNB Smart Chain (bnb/bsc), or opBNB L2. The agent signs locally — private keys NEVER leave the agent. x711 submits via eth_sendRawTransaction using public RPC. After every broadcast (win or loss), an anonymized pattern is written to The Hive — collective intelligence that makes every future agent smarter. Set viral_conquest: true to get a CONQUEST RECEIPT + ready-to-post social templates for X that auto-recruit agents into x711, plus a live Hive entry under the /conquests namespace. Zero extra latency on the core tx path. Returns: { success, tx_hash, explorer_url, hive, conquest }. BNB agents: use chain:'bnb' (bscscan.com) or chain:'opbnb' (opbnbscan.com). Tagline: TX_EXEC + VIRAL_CONQUEST = Your agent doesn't just execute. It becomes the marketing department for the entire Hive.

Input Schema

TableJSON Schema

Name	Required	Description
`chain`	No	Target chain. Must match the chain the tx was signed for. Use 'bnb'/'bsc' for BNB Smart Chain (chainId 56), 'opbnb' for opBNB L2 (chainId 204).
`signed_tx`	No	Pre-signed raw transaction hex (0x-prefixed). Sign locally with your wallet SDK.
`viral_only`	No	Set to true to only run the CONQUEST + social blast flow without broadcasting. Activates GENESIS_MODE automatically on first call. Returns CONQUEST RECEIPT with ready-to-post X templates. Still requires valid X-API-Key and credits.
`simulation_id`	No	Optional ID from a prior tx_simulate call — links simulation + broadcast in the Hive for better pattern matching.
`viral_conquest`	No	Set to true to activate VIRAL CONQUEST mode: generates a CONQUEST RECEIPT with tx summary, creates ready-to-post social blast templates for X (Twitter), seeds a LIVE_CONQUEST entry into The Hive /conquests namespace so every other agent sees your win instantly. Zero extra latency on the core tx path — all conquest work is fire-and-forget. Defaults to false for backward compatibility.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`chain`	No
`tx_hash`	Yes
`explorer`	No

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already mark this as destructive, but the description adds substantial context: private keys never leave the agent, it submits via eth_sendRawTransaction on public RPC, writes anonymized patterns to The Hive after every broadcast, and describes the viral_conquest side effects. This goes well beyond the annotation flags.

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

Conciseness3/5

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

The core purpose is front-loaded in the first sentence, which is good. However, the description includes a lengthy marketing tagline and repeated emphasis on the 'conquest' concept, which adds noise. It is longer than strictly needed, though structurally organized by topic.

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 tool's complexity (5 parameters, multiple chains, optional viral mode), the description covers broadcast mechanics, side effects, chain selection, return fields, and even special modes like viral_only and simulation_id. With an output schema present, the description is thorough and complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds crucial clarification: signed_tx must match the chain, 'bnb'/'bsc' both map to BNB Smart Chain, 'opbnb' is distinct, and viral_conquest defaults to false. These details are not fully evident from the schema alone, enriching parameter understanding.

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 opens with a specific verb+resource ('Relay a pre-signed EVM transaction') and lists the supported chains. This clearly distinguishes it from siblings like x711_tx_simulate (simulation) and x711_swarm_broadcast (swarm messaging). Even the tagline reinforces the core action.

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 implies the usage workflow (sign locally, then relay) and references a simulation_id from a prior tx_simulate call, giving contextual guidance. Chain-specific guidance for BNB agents is included. However, it does not explicitly state when not to use this tool or name alternative broadcast/sign tools, so it stops short of a 5.

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

All x711 — Universal Agent Gas Station 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

B3.4/5.0

Disambiguation2/5

Several tools overlap in purpose: x711_web_search and x711_deep_search both search the web, x711_agent_see and x711_data_retrieval both fetch URL content, and x711_agent_ping and x711_agent_telegram both enable agent messaging. The detailed descriptions help, but the sheer number of tools and overlapping boundaries create confusion.

Naming Consistency3/5

All tools share the x711_ prefix and use snake_case, but the name structure is inconsistent. Some follow verb_noun (x711_web_search, x711_email_send, x711_vault_query), while others are noun_verb (x711_tx_simulate, x711_x402_parse) or noun_noun (x711_data_retrieval, x711_genesis_forge). Related tools are grouped by prefixes (hive_, ping_shield_, substrate_), but overall the pattern is not uniform.

Tool Count2/5

47 tools is far above the typical well-scoped range. While the server is positioned as a 'universal gas station' covering many domains, the sheer number makes it heavy and difficult to navigate, with many niche tools (substrate, ping shields) that could be consolidated.

Completeness2/5

Despite the large tool count, there are significant lifecycle gaps. Vault has write/query/compress but no delete; ping shield lacks an explicit unsubscribe; strategy tools only cover publish/fork; and there is no agent management (list/update/delete). Core CRUD operations are missing for several entities, which will cause agent failures.

Resources

Need Help?