Skip to main content
Glama

Submit a signed transaction

submit_transaction
DestructiveIdempotent

Submit a signed vault transaction (from build_swap, signed by the user) to Stellar mainnet and wait for the result: status, hash, explorer link and the amount bought. Only relays calls to the vault.

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": {
      "xdr": "<xdr>"
    },
    "name": "submit_transaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
xdrYesThe signed transaction envelope, base64.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already flag destructive=true, openWorldHint=true and idempotentHint=true, so the safety profile is declared; the description adds value by disclosing that it targets Stellar mainnet (real funds), that it blocks and waits for the final result rather than returning a pending handle, and that it 'only relays calls to the vault' (no local key custody). It does not explain failure semantics, e.g. whether an on-chain failure returns an error or a non-success status field, which matters for a destructive mainnet write.

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?

Two dense sentences: the action and its source come first, the result payload second, and a scoping caveat last. No filler, nothing repeated from the title or annotations.

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?

There is no output schema, yet the description enumerates the meaningful return fields (status, hash, explorer link, amount bought), so an agent knows what it gets back. Slightly incomplete on error/failure handling and on why the call is idempotent, but nothing critical is missing for a single-parameter tool.

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

Parameters4/5

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

With one parameter at 100% schema coverage, the schema already documents 'xdr' as a base64 signed envelope, so the baseline is 3. The description earns the extra point by specifying the envelope's origin and state (produced by build_swap, already signed by the user), which is the main way an agent could misuse this parameter.

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 and resource ('Submit a signed vault transaction') plus the target network (Stellar mainnet) and the input's provenance ('from build_swap, signed by the user'). This clearly separates it from build_swap (which produces the unsigned transaction) and get_transaction (which retrieves one by hash).

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 phrase 'from build_swap, signed by the user' establishes the prerequisite ordering: build, sign, then submit, so an agent knows not to call this with an unsigned envelope. It also implies that no separate polling call is needed because the tool waits for the result, though it never explicitly says when not to use it or names get_transaction as the alternative for already-submitted hashes.

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.