Skip to main content
Glama

APEX x402 & AI Agent Tools (360 tools)

Arc exit weather

arc_exit_weather

Before your treasury parks idle USDC in an Arc lending vault: can that amount come back out? Live on-chain exit liquidity vs the 24 h low: CLEAR / TIGHT / BLOCKED / COULD_NOT_READ. Without a vault, names the highest-rate Arc USDC vault that can still return the amount. EIP-712 signed. Paid per call over x402.

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": {
      "amount": "<amount>"
    },
    "name": "arc_exit_weather"
  }
}

Input Schema

NameRequiredDescriptionDefault
vaultNooptional: the Arc vault address (0x...)
amountYesUSDC you may need back out (e.g. 25000)
paymentNoa signed x402 payment (base64, as in PAYMENT-SIGNATURE); the purchase completes inside this tool call

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/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 burden, and it does disclose several non-obvious traits: the result is derived from live on-chain exit liquidity benchmarked against the 24 h low, the call is EIP-712 signed, and it is paid per call over x402 (with the purchase completing inside the call). What is missing is anything about cost magnitude, rate limits, or what the agent should do on TIGHT versus BLOCKED.

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 decision the agent is trying to make, then the output vocabulary, then the no-vault fallback. Dense but every clause carries information. The telegraphic fragment style ('Live on-chain exit liquidity vs the 24 h low') is slightly harder to parse than plain prose but is not padded.

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 three params, no annotations, and no output schema, the description does the important work of enumerating the four possible status values, which effectively substitutes for a return-value spec. Remaining gaps are minor: how the 24 h low is computed and what action TIGHT implies. For a read-only pre-flight check this is close to sufficient.

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 already 100%, so the baseline is 3; the description adds genuine meaning beyond it by explaining the behavior when the optional vault is omitted — it falls back to naming the highest-rate Arc USDC vault that can still return the amount. That fallback semantics is not in the schema and directly affects how an agent calls the tool. It does not add anything about the payment parameter beyond what the schema says.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a concrete question — whether a given USDC amount can come back out of an Arc lending vault — and names the graded outcomes (CLEAR / TIGHT / BLOCKED / COULD_NOT_READ), which is far more specific than the title. It does not, however, distinguish itself from the many similarly named siblings such as arc_exit_check, exit_check, base_exit_check, or arc_exit_check_bulk, so an agent cannot tell from the text alone why this one differs.

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

Usage Guidelines3/5

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

The opening clause gives a clear decision point: run this before parking idle treasury USDC in an Arc vault. That is useful timing context. But there are no exclusions and no named alternatives, and with five exit-check siblings in the catalog the lack of routing guidance is a real gap.

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.