Skip to main content
Glama
Sign In

Insight Pre-Trade Safety

by io.github.imokokok
OverviewDiscussionsAdmin

issue_execution_receipt

Close the loop after an agent executes: issue a signed execution-price receipt from the pre-trade handle plus the settlement transaction, or settle a guarded Base/Solana swap. Use it only after the trade settled. Do not use it before execution and do not treat the verdict as principal authorization. Returns a signed receipt or settlement with FAITHFUL/DEVIATED/NOT_EXECUTED/UNDETERMINED (or settlement status), price delta, binding ids and verify URL. Deprecated alias: prefer trade_proof with op "issue_receipt". Removed on 2027-01-06.

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": {
      "mode": "<mode>"
    },
    "name": "issue_execution_receipt"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeYes
receiptNoRequired for mode=receipt; old execution_receipt fields
decisionNoRequired for settle modes; the signed guard decision
signatureNoSolana transaction signature
swap_tx_hashNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it does well: it discloses the returned verdict vocabulary (FAITHFUL/DEVIATED/NOT_EXECUTED/UNDETERMINED), price delta, binding ids, and a verify URL, plus a deprecation/removal date. It does not cover authorization requirements, idempotency of re-issuance, or rate limits, which keeps it below a 5.

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 core action and the post-settlement precondition are front-loaded, and most sentences carry real information. The deprecation and removal-date sentence plus the return-value enumeration make it dense as a single unbroken block, but little is genuinely redundant.

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 five-parameter, mode-switched mutation tool with nested objects and no output schema, the description supplies the return shape and the critical timing constraint that the schema cannot express. Gaps remain around mode selection guidance and any permission prerequisites, but nothing essential for a correct invocation 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 description coverage is 60%, so the schema already explains the receipt and decision objects and the Solana signature. The description adds conceptual mapping ('pre-trade handle plus the settlement transaction') but never explains the mode enum values or the swap_tx_hash parameter, which has no schema description at all.

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 specific verbs and resources: issuing a signed execution-price receipt from a pre-trade handle plus settlement transaction, and settling a guarded Base/Solana swap. It explicitly distinguishes itself from the sibling trade_proof, calling itself a deprecated alias and pointing to trade_proof with op "issue_receipt", 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?

It gives an explicit precondition ('Use it only after the trade settled'), an explicit exclusion ('Do not use it before execution'), a semantic caution ('do not treat the verdict as principal authorization'), and a named alternative (trade_proof). All three of when, when-not, and alternatives are present.

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

All Insight Pre-Trade Safety toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources