Skip to main content
Glama

Arc exit check

arc_exit_check

ARC ONLY. SELL TEST AT YOUR SIZE (not a score). If I put in this much, can I get out? For a token address or Uniswap v4 pool id on Arc, at the size you pass (usdc, default 1): a real buy-then-sell round trip inside one eth_call through the pool hook (nothing spent) or, for ERC-20-USDC pools, both legs quoted. Returns whether the sell goes through, the round-trip cost, depth, whether the pool owner can pull the liquidity, and flags with reasons. The answer names its method. For one 0-100 buy score with no size needed, use arc_verdict. For up to 25 tokens in one call use arc_exit_check_bulk. PAID: $0.025 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1; no key, no sign-up) at https://apexfaucet.xyz/api/x402/arc-exit-check-bulk?ids=. Over MCP this tool answers with that price and URL, not the data.

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": {
      "query": "<query>"
    },
    "name": "arc_exit_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
usdcNoTest size in USDC, default 1, max 1000.
queryYesToken address (0x + 40 hex) or v4 pool id (0x + 64 hex).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does: it discloses that the round trip runs inside one eth_call through the pool hook and spends nothing, that ERC-20-USDC pools quote both legs, and what the result reports (sell success, round-trip cost, depth, owner pull ability, flags). It also discloses the paid x402 flow and, critically, that over MCP the tool returns a price and URL rather than data.

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 the core definition ('SELL TEST AT YOUR SIZE') and then alternatives, payment, and caveat in a sensible order. It is dense and somewhat run-on, with a few parenthetical asides, but nearly every sentence carries information an agent needs.

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?

There is no output schema, and the description compensates by enumerating what is returned (whether the sell goes through, round-trip cost, depth, owner liquidity pull risk, flags with reasons, and the method used). For a paid simulation tool, the pricing channels and the MCP-vs-HTTP behavior are also spelled out, so nothing needed to call it correctly is missing.

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 the baseline is 3, but the description adds meaning by framing usdc as the test size at which the exit is simulated and clarifying that query is either a token address or a v4 pool id. It does not repeat the max-1000 or hex-format constraints already in the schema, which is appropriate.

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: a sell test / buy-then-sell round trip at a chosen size for a token address or Uniswap v4 pool id on Arc. It explicitly distinguishes itself from arc_verdict (a score) and arc_exit_check_bulk (bulk), so an agent can pick it without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Gives explicit routing: use arc_verdict for a 0-100 buy score with no size, arc_exit_check_bulk for up to 25 tokens, and this tool for a single sized exit test. It also scopes it with 'ARC ONLY', leaving no ambiguity about when this is the right call.

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