Skip to main content
Glama

game_submit_tx

Destructive

[STATE] Submit a signed Solana transaction for any game step — same-chain (deposit_stake, join_game, commit_guess, reveal_guess, create_game) or cross-chain (create_xmatch, lock_xtranche, settle_xmatch, refund_xmatch_timeout, refund_xmatch_nocert, built by the xchain_build_* tools). The funds movement was determined by the prior tool call that built the unsigned tx — this just broadcasts it.

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": {
      "signed_transaction": "<signed_transaction>",
      "action": "<action>"
    },
    "name": "game_submit_tx"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesThe action this transaction performs. Same-chain: "deposit_stake", "join_game", "commit_guess", "reveal_guess", "create_game". Cross-chain (built by the `xchain_build_*` tools): "create_xmatch", "lock_xtranche", "settle_xmatch", "refund_xmatch_timeout", "refund_xmatch_nocert".
networkNoSolana network. `"mainnet"` (default) or `"devnet"`. Must match the network used to build the unsigned tx — broadcasting to the wrong cluster = `BlockhashNotFound` rejection.
signed_transactionYesBase64-encoded signed Solana transaction.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, openWorldHint=true and idempotentHint=false, so the safety profile is covered. The description adds the useful semantic point that this call merely broadcasts a pre-determined transfer, but it says nothing about failure handling, duplicate submission, or what happens on rejection beyond the network note that lives in the schema.

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?

Two tight, front-loaded sentences preceded by a state tag; the first sentence efficiently enumerates the valid actions and the second explains the broadcast semantics. The action enumeration is somewhat redundant with the schema but aids routing at a glance.

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?

For a destructive, non-idempotent broadcast tool with no output schema, the description never indicates what comes back (signature, confirmation status, error surfaces) an agent would need to verify success. The preconditions and action coverage are complete, but the post-call contract is missing.

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%, including the action enum-like list and the network/BlockhashNotFound warning, so the schema carries the load. The description's action list duplicates the schema's action field rather than adding new meaning such as encoding or confirmation requirements.

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 (Submit) and resource (a signed Solana transaction) and enumerates the exact actions it covers across same-chain and cross-chain flows. It explicitly separates itself from the xchain_build_* tools that produce the unsigned transaction, so an agent can distinguish it from siblings without opening a schema.

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?

Makes the ordering constraint explicit: it must be used after the tool that built the unsigned tx, since funds movement is already determined. It also implicitly scopes to Solana (not the game_evm_* flow), though it never names the EVM alternatives or states what to do if no build step preceded it.

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