Skip to main content
Glama

Exit check bulk

exit_check_bulk

PAYWALLED. Portfolio exit analysis — pass up to 25 mints and get back which of your positions cannot be sold cleanly, ranked worst first. Answers "of everything I hold, what am I trapped in?" in one call. Returns x402 payment instructions for /api/x402/exit-check-bulk. For one token use exit_check; this one is for portfolios.

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": {
      "mints": "<mints>"
    },
    "name": "exit_check_bulk"
  }
}

Input Schema

NameRequiredDescriptionDefault
usdNoPosition size in USD to test each holding at. Optional.
mintsYesUp to 25 token mint addresses.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior3/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 it does disclose important traits: PAYWALLED, returns x402 payment instructions for /api/x402/exit-check-bulk, batch cap of 25, and worst-first ranking. It does not say what the call costs, whether partial failures on individual mints are tolerated, or what happens if more than 25 mints are passed.

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-loads the key operational fact (PAYWALLED), then purpose, then the sibling routing rule — a sensible order with little waste. The rhetorical "what am I trapped in?" sentence is slightly redundant with the preceding sentence but does reinforce the framing.

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 two-parameter analysis tool with no output schema, the description covers input limits, output semantics (ranked worst-first list of unsellable positions), and the payment gate. The main gap is that it never explains how an agent should act on the returned x402 payment instructions.

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 description coverage is 100%, so both parameters are already documented in the schema, and the description only restates the 25-mint cap. The `usd` parameter is not mentioned in the description at all, but the schema covers it, so the baseline of 3 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 ("Portfolio exit analysis"), the input form ("pass up to 25 mints"), and the output shape ("which of your positions cannot be sold cleanly, ranked worst first"). It explicitly differentiates itself from the sibling arc_exit_check by declaring it is for portfolios, not single tokens.

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 an explicit alternative and the condition that selects it: "For one token use exit_check; this one is for portfolios." Combined with the 25-mint cap, an agent knows exactly when this tool applies versus its nearest sibling.

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