Skip to main content
Glama

Pre-sign transaction check

precheck_transaction
Read-onlyIdempotent

Check a Robinhood Chain transaction before it is signed. Send the transaction you are about to sign and get back pass, warn or block with the reasons behind it.

Call this on every transaction that approves, transfers or swaps a token on Robinhood Chain (chain 4663), and before any approval to a spender you have not used before. It catches drainer contracts, broad approvals to unknown spenders, lookalike Stock Tokens (read live from the token's own ticker and name), and a size larger than the pools can take. Zorvu does not grade the liquidity, holders or sellability of tokens that are not official Stock Tokens: such a token comes back token_not_graded (info), and archived readings never count as a pass. Pass intent.usd to have the size checked against measured sell depth, and policy to enforce your own ceilings.

pass means the transaction passed the checks listed in checks_run at the time shown in checked_at, nothing broader. It does not mean the transaction is safe, and it is not a promise about what the transaction will do. warn and block are Zorvu's measurements, not instructions and not advice: you decide. Zorvu never builds, routes, signs or sends a transaction, holds no keys, and charges no fee.

Anything Zorvu could not read comes back null with a reason code saying so, never as a pass. mode: "fast" skips live chain reads; what it gives up is listed in each not_checked_fast reason. Needs a Zorvu API key in the Authorization header of your MCP client config, never as an argument. Not financial advice.

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_id": "<chain_id>",
      "tx": "<tx>"
    },
    "name": "precheck_transaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
txYesThe transaction you are about to sign.
modeNofast: no live chain reads, for an answer in well under a second.
intentNo
policyNoYour own limits.
chain_idYesRobinhood Chain. The only chain supported.

Output Schema

NameRequiredDescriptionDefault
modeYes
depthYes
tokensYes
decodedYes
reasonsYes
verdictYes
checked_atYes
checks_runYesThe checks that ran. pass covers only these.
disclaimerYes
api_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: no key custody, no routing/signing/sending, no fee, unreadable fields return null with a reason code rather than a pass, `mode: "fast"` skips live chain reads with the tradeoff enumerated in not_checked_fast, and the API key must live in client config rather than an argument. These are operational facts an agent cannot obtain from the readOnly/idempotent hints alone.

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?

Front-loaded with purpose and return values, then decision guidance, then caveats — a sensible order for a high-stakes check. It is on the long side and repeats the non-advice disclaimer across several sentences ('not instructions and not advice', 'Not financial advice'), which costs some density without adding new information.

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 5-parameter, nested-object tool with an output schema, it covers everything an agent needs: verdict semantics, the meaning of a pass (scoped to checks_run at checked_at), null-handling, auth placement, and fast-mode degradation. Return-value detail is correctly left to the output schema rather than duplicated.

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

Parameters4/5

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

Schema coverage is 80%, so baseline is 3, and the description earns above that by explaining what intent.usd and policy actually do (size checked against measured sell depth; enforce your own ceilings; context for broad-approval detection) and by flagging that fast mode degrades coverage. It does not spell out chain_id's const or tx.from/value handling, leaving some meaning to the schema.

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 and resource — 'Check a Robinhood Chain transaction before it is signed' — plus the return contract (pass/warn/block with reasons). It also draws the boundary of its own scope by stating it does not grade liquidity/holders/sellability of non-Stock-Tokens, which separates it from the token-lookup siblings.

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?

Gives explicit when-to-call guidance: 'every transaction that approves, transfers or swaps a token' and 'before any approval to a spender you have not used before', plus when to supply intent.usd and policy. It stops short of naming an alternative tool or saying flatly when not to call it, so the routing is inferential on the negative side.

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.

Resources