Skip to main content
Glama

arcanumfleet-mcp-server

ArcanumFleet Solana Tx Simulator

arcanum_tx_simulate
Read-onlyIdempotent

Use this before signing a Solana transaction to simulate it via RPC and check for execution errors, compute units, and authority-change risks. Costs 0.005 USDC via x402.

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": {
      "tx_base64": "<tx_base64>"
    },
    "name": "arcanum_tx_simulate"
  }
}

Input Schema

NameRequiredDescriptionDefault
tx_base64YesBase64-encoded serialized Solana transaction

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Beyond the readOnly/openWorld/idempotent annotations, it discloses the transport ('via RPC') and a paid cost of 0.005 USDC via x402, which is meaningful behavioral context an agent cannot get from the annotations. It does not explain response shape or what happens when simulation fails, but with no output schema and safe-read annotations, this is a solid contribution.

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 compact sentences: the first front-loads the when-to-use and the outcome being checked, the second adds the cost. Nothing is redundant or padded.

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?

For a single-parameter, annotation-covered read tool, the description covers purpose, timing, returned signals, and payment cost, which is nearly everything needed. The remaining gap is failure semantics and result format, minor given no output schema.

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 only one parameter and the input schema already describes it fully as a 'Base64-encoded serialized Solana transaction' at 100% coverage. The description adds no encoding details, size limits, or accepted transaction versions beyond that, so the schema does all the work and the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('simulate' a 'Solana transaction') and enumerates what the simulation surfaces: execution errors, compute units, and authority-change risks. It does not name any sibling, but none of the listed siblings (audit, jupiter_quote, liquidity_check, etc.) appear to compete with this function, so the distinction is largely implicit.

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?

It gives explicit timing guidance ('Use this before signing a Solana transaction'), which tells the agent exactly where in a workflow to invoke it. It stops short of naming alternatives or exclusions, but the pre-signing precondition is clear context.

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.