Skip to main content
Glama

APEX Agent Safety & Guardrails

Tx check

tx_check

Free sample: https://apexfaucet.xyz/tx-check ($0.001). Check one unsigned Base or Solana transaction and return SAFE or RISKY. Base: simulation, unlimited approval, approval-for-all, a hidden token move, and one exit check. Solana: simulation, a token drain, a delegate approval, and a rug mint. Nothing is signed or broadcast. $0.001 per call over x402 (USDC on Base or USDC on Solana only). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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": "tx_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoBase contract (0x...), required unless raw is set
txNounsigned Solana transaction, base64 or base58
rawNoBase serialized unsigned transaction, or the Solana transaction when tx is omitted
dataNoBase 0x calldata, required unless raw is set
fromNoBase sender (0x...), or the Solana signer when signer is omitted
chainNobase (default) or solana
valueNoBase native value in wei
signerNoSolana account that would sign
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so well: it states that nothing is signed or broadcast (the key safety property for a pre-signature check), discloses exactly what is inspected per chain, and specifies the cost and payment rail ($0.001 per call, USDC on Base or Solana only). It also explains that the purchase completes inside the call when `payment` is passed, which is non-obvious behavior.

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 opening SAFE/RISKY verdict and the unsigned/no-broadcast guarantee are front-loaded, and the paragraph stays tight despite covering checks, pricing, and the payment flow. It loses a point for the promotional sample URL and for repeating the $0.001 price twice, which is redundant text an agent does not need.

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 9-parameter tool with no annotations and no output schema, the description covers the essentials: what is returned (SAFE or RISKY), what is examined, the chain split, and the payment protocol. Remaining gaps are moderate — it never says how the Base and Solana parameter sets interact, what happens on an unsupported chain, or what an inconclusive/error result looks like.

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 description coverage is 100%, so baseline is 3, but the description adds real meaning on top of the schema by explaining the two-call payment handshake that governs the `payment` parameter — pass it and the purchase completes in-call. It also clarifies the chain scope that drives whether the Base params (to/data/raw) or Solana params (tx/signer) apply, though it never states which fields are mutually exclusive.

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 gives a specific verb and resource — 'Check one unsigned Base or Solana transaction and return SAFE or RISKY' — and enumerates the exact risk classes examined per chain (unlimited approval, approval-for-all, hidden token move, exit check on Base; token drain, delegate approval, rug mint on Solana). It does not name or differentiate itself from nearby tools like evm_tx, tx_explain, or arc_bundle_check, so an agent must infer the boundary itself.

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 clearly scopes usage to one unsigned transaction on Base or Solana and gives explicit procedural guidance for the paid flow: call once without `payment` to get terms, sign with your own wallet, call again with `payment`. It does not state when to prefer this over sibling checkers such as evm_tx or tx_explain, so alternatives remain unaddressed.

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.