Skip to main content
Glama

Base exit check

base_exit_check

BASE ONLY, EXECUTED (not a quote). Can you get out of a Base token, and what does it cost? Executes a buy and a full sell through its deepest pool we can simulate (Uniswap v2/v3/v4 against WETH or ETH, Virtuals agent tokens through their VIRTUAL pool, Aerodrome basic and Slipstream pools) in one simulated Base block and returns the ETH that comes back, the round-trip cost and the revert reason if a leg fails. $0.01 per call over x402 (Base USDC first).

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

Input Schema

NameRequiredDescriptionDefault
tokenYesthe Base token contract address (0x...)
paymentNoa signed x402 payment (the same base64 payload you would put in the PAYMENT-SIGNATURE header). Pass it here and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

No annotations exist, so the description carries the full load and does so well: it discloses that this is a real execution rather than a quote, that both legs run in one simulated Base block, that a failed leg returns a revert reason, and that it costs $0.01 per call via x402 with Base USDC settled first. What it leaves unstated is whether the simulated buy has any real cost or side effects and whether calls are rate limited.

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 critical constraint and the core question are front-loaded, and the closing sentence covers cost and settlement. The long parenthetical enumerating venues is dense but carries genuine scoping information, so little is wasted.

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 steps up by naming the returned fields: ETH back, round-trip cost, and revert reason. For a two-parameter simulation tool this is nearly complete; only the interpretability of the returned numbers (gross vs. net of fees) is left to the caller.

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 100%, so both `token` and `payment` are already documented in the input schema; the description adds only indirect support by explaining the x402 pricing that motivates the payment payload. It gives no extra meaning about address format, supported token standards, or what happens if payment is omitted.

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?

"Executes a buy and a full sell through its deepest pool we can simulate" states a specific verb and resource with scope, and "BASE ONLY, EXECUTED (not a quote)" immediately separates it from chain siblings like arc_exit_check and exit_check. An agent can pick this over the arc/other-chain variants without opening a 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?

The "BASE ONLY" prefix and the framing "Can you get out of a Base token, and what does it cost?" set a clear use context, and the venue list clarifies which token types are covered. It stops short of naming the alternative tool to use for non-Base chains or bulk runs, so the agent must infer the routing to arc_exit_check or exit_check_bulk.

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