Skip to main content
Glama

Diogenes Web3, DeFi & 402 Security MCP

Pre-Sign Calldata Simulator & Stateful Blockchain Transaction Tracker

simulate_evm_transaction_calldata
Read-onlyIdempotent

Simulates raw EVM hex calldata (0x...), estimates gas/fees for pre-sign payload assembly, and tracks on-chain transaction execution state, confirmations, and receipts. Use when auditing calldata before signing or tracking execution state and confirmations after broadcast; for inspecting off-chain EIP-712 typed-data signatures, use decode_eip712_permit_signature instead. Stateless read-only edge call (max 32 KB, 60 RPM): accepts 'action' ('network' defaults to 'base_mainnet'), supports '?demo=true' or L402 (20 sats), and returns HTTP 400 if invalid.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "simulate_evm_transaction_calldata"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionNoOperation: 'simulate_calldata' to simulate/decode, 'prepare_transaction' to assemble payload, or 'track_tx_state'.
networkNoTarget EVM network for simulation context; defaults to 'base_mainnet' when omitted.
tx_hashNoTransaction hash (0x...) to track on-chain execution state and confirmation depth.
calldata_hexNoHexadecimal EVM transaction data string starting with '0x' (e.g. '0x095ea7b3000000000000000000000000...').

Output Schema

NameRequiredDescriptionDefault
tx_stateNoOn-chain transaction execution state, block height, and confirmation count.
selector_hexYesExtracted 4-byte function selector (e.g. '0x095ea7b3').
decoded_methodYesHuman-readable ABI function signature matched to the selector.
prepared_payloadNoUnsigned transaction payload with estimated gas and nonce ready for wallet signing.
simulation_verdictYesPre-sign safety recommendation ('SAFE_CALLDATA' or 'HIGH_RISK_APPROVAL_DETECTED').

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / properties / action
      Added value: +{
      +  "description": "Operation: 'simulate_calldata' to simulate/decode, 'prepare_transaction' to assemble payload, or 'track_tx_state'.",
      +  "enum": [
      +    "simulate_calldata",
      +    "prepare_transaction",
      +    "track_tx_state"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / tx_hash
      Added value: +{
      +  "description": "Transaction hash (0x...) to track on-chain execution state and confirmation depth.",
      +  "type": "string"
      +}
    • removedInput schema / required
      Removed value: -[
      -  "calldata_hex"
      -]
    • removedOutput schema / properties / approval_or_drain_risk
      Removed value: -{
      -  "description": "True if the call grants token/NFT allowances or transfers assets to an untrusted target.",
      -  "type": "boolean"
      -}
    • addedOutput schema / properties / prepared_payload
      Added value: +{
      +  "description": "Unsigned transaction payload with estimated gas and nonce ready for wallet signing.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / tx_state
      Added value: +{
      +  "description": "On-chain transaction execution state, block height, and confirmation count.",
      +  "type": "object"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "selector_hex",
      -  "decoded_method",
      -  "approval_or_drain_risk",
      -  "simulation_verdict"
      -]New value: +[
      +  "selector_hex",
      +  "decoded_method",
      +  "simulation_verdict"
      +]
  2. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description goes well beyond them with a 32 KB payload cap, 60 RPM limit, demo flag or L402 payment of 20 sats, a default network, and HTTP 400 on invalid input. Remaining gap is how confirmations/receipts mature over time and any eventual-consistency behavior for tracking.

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?

Purpose is front-loaded in the first sentence, followed by routing guidance and then operational constraints. The final sentence is a dense run-on packing size, rate, payment, default, and error behavior together, which costs a little readability.

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?

For a three-mode read-only tool with a 100% documented schema and an output schema, the description covers purpose, routing, limits, payment/auth, defaults, and error behavior. Nothing an agent needs to invoke it correctly 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 coverage is 100% and enum descriptions already explain action and network semantics, so the baseline of 3 applies. The description restates the base_mainnet default and adds a size constraint on calldata_hex but no new per-parameter meaning, such as which parameters each action requires.

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?

Names concrete verbs and resources: simulates raw EVM hex calldata, estimates gas/fees, and tracks on-chain execution state, confirmations, and receipts. It also explicitly carves itself away from the sibling decode_eip712_permit_signature, so an agent can choose correctly without opening schemas.

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 explicit when-to-use conditions (auditing calldata before signing, tracking execution after broadcast) and names the alternative tool plus the condition that selects it (off-chain EIP-712 typed-data inspection). No inference required.

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.