Skip to main content
Glama

EVE Frontier Sui Move PTB Coin-Drain & HotPotato Safety Simulator

simulate_eve_sui_ptb
Read-onlyIdempotent

Simulate Sui Programmable Transaction Block sequences to detect unauthorized coin splits, object transfers, and unconsumed HotPotato receipts before signing untrusted EVE Frontier bundles.

Instructions

Simulates Sui Programmable Transaction Block (PTB) command sequences to detect unauthorized coin splits, object transfers, and unconsumed HotPotato receipts. Use when auditing an untrusted EVE Frontier transaction bundle before signing with a pilot wallet; for verifying pilot zkLogin JWT proofs and character ownership capabilities, use verify_eve_zklogin_character instead. Stateless read-only edge call (max 32 KB, 60 RPM): accepts 'ptb_commands_json' ('strictness_mode' defaults to 'strict_zero_drain'), supports '?demo=true' or L402 (35 sats), and returns HTTP 400 if invalid.

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": {
      "ptb_commands_json": "<ptb_commands_json>"
    },
    "name": "simulate_eve_sui_ptb"
  }
}

Input Schema

NameRequiredDescriptionDefault
strictness_modeNoSimulation policy controlling whether multi-transfer PTBs are blocked; defaults to 'strict_zero_drain' when omitted.
ptb_commands_jsonYesJSON-serialized array of PTB commands or comma-separated Move calls (e.g. '[{"kind":"SplitCoins"},{"kind":"MoveCall"}]').

Output Schema

NameRequiredDescriptionDefault
signing_verdictYesFinal safety recommendation ('SAFE_EVE_FRONTIER_PTB' or 'BLOCK_SUSPICIOUS_PTB_DRAIN').
ptb_command_countYesNumber of PTB commands statically simulated.
hot_potato_receipts_balancedYesTrue if every Move HotPotato struct created in the PTB is consumed before exit.
hidden_coin_transfer_detectedYesTrue if unauthorized SplitCoins or TransferObjects drains are detected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.6.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, but the description adds operational behavior the annotations don't: stateless edge call, 32 KB limit, 60 RPM, demo mode or L402 payment (35 sats), and HTTP 400 on invalid input. This is exactly the kind of extra behavioral context annotations cannot express.

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?

The sentence is dense but front-loads purpose before caveats, and every clause carries useful signal (use case, alternative, limits, auth). It is slightly packed with operational details in one paragraph, keeping it just below a 5.

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?

An output schema exists, so the description needn't explain return values. Given the two-parameter schema and rich annotations, the definition supplies everything an agent needs to call it correctly: scope, alternative, limits, auth, and failure behavior.

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%, so both parameters are already documented. The description restates the default for strictness_mode but adds no syntax or format details beyond the schema's own explanation of ptb_commands_json. Baseline 3 applies when the schema does the heavy lifting.

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 ('Simulates') and resource ('Sui Programmable Transaction Block (PTB) command sequences') plus the concrete detections (coin splits, object transfers, unconsumed HotPotato receipts). It explicitly distinguishes itself from verify_eve_zklogin_character, so an agent can route without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit use case ('auditing an untrusted EVE Frontier transaction bundle before signing with a pilot wallet') and names the alternative tool and its purpose ('for verifying pilot zkLogin JWT proofs and character ownership capabilities, use verify_eve_zklogin_character instead'). Both when-to-use and when-not are covered.

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

Deploy Server

Other Tools