Skip to main content
Glama

Arc exit check bulk

arc_exit_check_bulk

PAYWALLED. Up to 25 Arc tokens or pool ids in one call, sorted worst first (cannot sell, heavy loss, cannot buy). Returns x402 payment instructions for /api/x402/arc-exit-check-bulk ($0.025, USDC on Base first, also Arc and Solana, or XNT on X1). For one token use arc_exit_check.

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": {
      "ids": "<ids>"
    },
    "name": "arc_exit_check_bulk"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesUp to 25 token addresses or pool ids.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/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 well: it discloses the paywall, the exact price ($0.025), accepted currencies and chains (USDC on Base first, also Arc and Solana, or XNT on X1), and that the immediate return value is x402 payment instructions rather than the analysis itself. It stops short of explaining what happens after payment (how results are retrieved) or whether any auth/quota applies, which keeps it below a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the PAYWALLED flag, then the capability, then the payment detail, then the routing hint. No filler; each sentence carries information the agent needs.

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 single-parameter, no-output-schema tool, the definition covers cost, payment rails, item limit, ordering semantics, and the alternative tool. The only real gap is the post-payment flow — what the agent must do once payment instructions are returned — which an agent would otherwise have to discover.

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?

One parameter with 100% schema description coverage sets the baseline at 3, and the description does add one piece of meaning: the 25-item ceiling and that entries may be either token addresses or pool ids. That is essentially a restatement of the schema's own text, so it is only a marginal gain.

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?

The description states a specific verb (exit check), resource (Arc tokens or pool ids), and scope (bulk, up to 25 in one call), and adds what the output is ordered by (worst first: cannot sell, heavy loss, cannot buy). It explicitly distinguishes itself from the single-token sibling arc_exit_check.

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?

It names the alternative explicitly and the condition that selects it: 'For one token use arc_exit_check.' Combined with the stated 25-item cap, an agent can route correctly between the bulk and single variants without inspecting either schema.

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