Skip to main content
Glama

solana_tx_simulate

Read-onlyIdempotent

Simulate a Solana transaction before signing it: balance changes, labeled programs, deterministic risk rules, and a proceed/caution/avoid recommendation. Free over MCP for 10 calls per day; beyond that the tool returns the pay-per-call x402 endpoint and its price.

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": {
      "transaction": "<transaction>"
    },
    "name": "solana_tx_simulate"
  }
}

Input Schema

NameRequiredDescriptionDefault
transactionYesBase64-encoded unsigned (or signed) Solana transaction

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world behavior, so the safety profile is covered. The description's real contribution is the quota disclosure: 10 free calls per day, after which it returns a pay-per-call x402 endpoint and price, which is genuinely useful operational context not present in annotations. It stops short of saying what a malformed or unparseable transaction yields, or which cluster is simulated.

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 sentences, front-loaded with the capability and its outputs, with the quota caveat following. The pricing detail is necessary to prevent surprise failures, though the x402 mention is slightly dense for a single clause.

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?

With no output schema, the description does carry the burden of describing returns, and it does so adequately by listing balance changes, labels, risk rules, and a recommendation. Missing pieces are meaningful for a simulation tool: which network/cluster is assumed, and what happens when the daily free quota is exhausted mid-workflow.

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?

There is a single parameter with 100% schema description coverage, so the schema already explains that a Base64 unsigned-or-signed transaction is expected. The description adds only the framing that the transaction is pre-signing; it supplies no additional encoding, size, or versioning constraints 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 names a specific verb and resource ("Simulate a Solana transaction") and enumerates the concrete outputs: balance changes, labeled programs, deterministic risk rules, and a proceed/caution/avoid verdict. That distinguishes it from generic siblings like tx_simulate and from solana_tx_explain by making clear it produces a forward-looking simulation rather than a decoding of past activity.

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 "before signing it" gives clear timing context: this is a pre-signature safety gate, not a post-hoc analysis tool. It does not, however, point to a specific alternative when simulation is not applicable (e.g., tx_decode or solana_tx_explain for already-executed transactions), so the routing guidance is implied rather than explicit.

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.