Skip to main content
Glama

APEX Agent Safety & Guardrails

Robinhood exit check

robinhood_exit_check
Read-onlyIdempotent

Real simulated buy-and-sell honeypot and exit check on Robinhood Chain (chain 4663) across up to 4 Uniswap v4 pools for a token address. $0.01 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for terms, sign with your own wallet, call again with payment.

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": {
      "token": "<token>"
    },
    "name": "robinhood_exit_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYesRobinhood Chain token contract address (0x + 40 hex)
paymentNosigned x402 payment payload (PAYMENT-SIGNATURE).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Adds substantial context beyond the annotations: cost ($0.01 per call), the payment rails accepted (USDC on Arc/Base/Solana or XNT on X1), the two-step auth handshake, and a coverage limit (at most 4 pools checked). The 'simulated' framing is consistent with readOnlyHint=true since no real swap is executed.

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?

Three dense sentences, with the core purpose front-loaded and the payment flow following. Every sentence carries information; only the granular currency list is arguably optional detail.

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 covers the call flow, pricing and scope limits, but does not describe what the check reports back (honeypot verdict, tax, sellability, per-pool results), leaving the agent to infer the return shape.

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 100%, so baseline is 3, and the description adds real meaning on top: it explains that `payment` is a signed payload produced by the caller's own wallet and that omitting it returns terms rather than performing the check, which the schema alone does not convey.

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 (simulated buy-and-sell honeypot/exit check), pins the chain (Robinhood Chain, chain 4663), the venue (up to 4 Uniswap v4 pools), and the input (token address). The chain qualifier lets an agent distinguish this from arc_exit_check or base_exit_check 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete invocation guidance: call once without `payment` to get terms, sign with your own wallet, then call again with `payment`. It does not explicitly say when to choose this over exit_check or token_exit_matrix, but the chain scoping makes the intended context clear.

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.