Insight Pre-Trade Safety

begin_trade_evidence

Open the verifiable execution loop: certify a swap/DeFi intent before the agent executes. Use it when a principal needs a signed pre-trade handle to bind an execution receipt later. Do not use it as trade authorization and do not call it after the trade. Returns preTradeUid, destinationPreTradeUid, requestHash, CAIP-19 asset ids, certified cross-rate, the 50 bps band, verdicts and the signed pre-trade attestations. Deprecated alias: prefer trade_proof with op "begin_evidence". 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": {
      "asset": "<asset>",
      "destination_asset": "<destination_asset>",
      "chain_id": "<chain_id>",
      "action": "<action>",
      "amount_usd": "<amount_usd>",
      "max_slippage_bps": "<max_slippage_bps>",
      "decision_input": "<decision_input>"
    },
    "name": "begin_trade_evidence"
  }
}

Input Schema

Name	Required	Description
`asset`	Yes	Source asset sold
`action`	Yes
`chain_id`	Yes	Execution chain id. Independent on-chain route quotes are currently available only on Ethereum mainnet (chain_id 1); other chains return [unavailable:unsupported_chain] without billing.
`providers`	No
`amount_usd`	Yes
`protocol_id`	No
`decision_input`	Yes	Required quote evidence: {source, destination, routeQuotePrice, routeQuoteObservedAt} (old camelCase shape)
`max_slippage_bps`	Yes	Pre-committed tolerance; fixed at 50
`destination_asset`	Yes	Destination asset bought
`source_group_count`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 9, 2026

changedInput schema / properties / chain_id / description

Previous value: -"Execution chain id"New value: +"Execution chain id. Independent on-chain route quotes are currently available only on Ethereum mainnet (chain_id 1); other chains return [unavailable:unsupported_chain] without billing."

AddedNov 6, 2026

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 does substantial work: it lists returned artifacts (preTradeUid, requestHash, CAIP-19 asset ids, certified cross-rate, 50 bps band, verdicts, signed attestations), flags deprecation and a hard removal date, and warns that the handle is not authorization. It stops short of auth requirements, handle expiry/idempotency, and failure behavior beyond what the schema mentions.

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?

Front-loaded with purpose, then exclusions, then return shape, then deprecation routing — a sensible priority order. Every sentence carries distinct information (trigger, prohibition, outputs, migration), with no filler.

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 10-parameter, 7-required nested-object tool with no output schema, the description covers purpose, prohibitions, return payload, chain support caveat, and deprecation adequately. Gaps remain around input field intent (providers, protocol_id, decision_input usage) and operational concerns like auth or handle lifetime.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

At 50% schema coverage across 10 parameters, the description should compensate but barely touches inputs. The only input-adjacent detail is the '50 bps band', which merely restates the schema's const 50; undocumented parameters like providers, protocol_id, source_group_count, and the action enum get no explanation, and the long return-value list does not help an agent fill the input.

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?

Opens with a specific verb+resource framing: 'Open the verifiable execution loop: certify a swap/DeFi intent before the agent executes.' It also distinguishes itself from the sibling trade_proof by naming the exact replacement call (op "begin_evidence") and giving a removal date, so an agent can route correctly without inspecting 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?

Explicitly states the trigger condition ('when a principal needs a signed pre-trade handle to bind an execution receipt later') and two negative cases ('Do not use it as trade authorization', 'do not call it after the trade'). It also names the preferred alternative, so when-to-use, when-not-to-use, and the substitute are all covered.

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 tools Inspect

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.