KushBitx AgentProof

Simulation Check

preflight

Read-onlyIdempotent

Simulation Check: simulate one unsigned Base transaction (eth_call and gas estimate), decode transfers, approvals and setApprovalForAll, and flag unlimited approvals, non-contract targets, the zero address, reverts and destination risk labels. Returns ALLOW, WARN, BLOCK or INCOMPLETE. For one ALLOW, REVIEW or BLOCK verdict before signing (effects, intended recipient, token, batches, signed verdict) use KushBitx Preflight: /api/preflight. Paid tool: 0.001 USDC per call on Base via x402 (exact scheme). An unpaid call returns the payment requirement and charges nothing.

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": {
      "chain": "<chain>",
      "to": "<to>"
    },
    "name": "preflight"
  }
}

Input Schema

Name	Required	Description
`to`	Yes	Transaction destination.
`data`	No	Unsigned calldata.
`from`	No	Optional sender used for simulation.
`chain`	Yes
`valueWei`	No	Native ETH value in wei.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantial context: what gets decoded, which risks are flagged (unlimited approvals, non-contract targets, zero address, reverts, risk labels), the four possible verdicts, and the payment model (0.001 USDC on Base via x402 exact scheme, unpaid calls cost nothing and return the requirement). That is exactly the kind of disclosure annotations cannot carry.

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 and verdict set are front-loaded, and every clause carries information (decoded artifacts, risk flags, verdicts, payment terms). The middle sentences are dense and run long, but there is no filler to cut.

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?

With no output schema, the description correctly explains the return values (four verdict codes) and the paid-call behavior. What 'destination risk labels' mean and the shape of the decoded transfer/approval list are left unspecified, a minor gap for a read-only simulation tool.

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 80%, so the schema already defines to/data/from/chain/valueWei. The description adds no syntax or semantic detail beyond noting a single unsigned Base transaction, so it neither compensates for the remaining gap nor deepens parameter meaning. Baseline 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 one unsigned Base transaction, decode transfers/approvals/setApprovalForAll, and return ALLOW/WARN/BLOCK/INCOMPLETE. It explicitly contrasts itself with KushBitx Preflight (/api/preflight), which yields a single verdict. The routing sentence muddles the boundary slightly since both surface a preflight-style verdict, keeping this just below a 5.

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 names the alternative (KushBitx Preflight: /api/preflight) and the condition selecting it — needing one ALLOW/REVIEW/BLOCK verdict before signing with effects, recipient, token, batches. However, it never states when this tool should NOT be used, and 'single unsigned transaction' scoping must be inferred.

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

All KushBitx AgentProof 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.

Resources

Need Help?