Skip to main content
Glama

APEX DeFi, DefiLlama & 8-Chain EVM Intel

Token exit matrix

token_exit_matrix
Read-onlyIdempotent

Multi-size DEX token liquidity, sell slippage, AMM price impact curve, and honeypot/exit risk matrix across USD position tiers before trading. Not advice. $0.004 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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

Input Schema

NameRequiredDescriptionDefault
chainNooptional chain filter: ethereum, base, arbitrum, optimism, polygon, bnb, arc, robinhood or solana
tokenYestoken contract address (0x + 40 hex on EVM) or base58 Solana mint
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.
sizesUsdNooptional 1 to 6 comma-separated USD position sizes to model (default 100,1000,10000,50000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world behavior, so the bar is lower. The description still adds material context the annotations cannot convey: it is a paid tool at $0.004 per call via x402, requires a two-step terms-then-payment handshake, and carries a 'not advice' disclaimer.

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 capability list is front-loaded and the payment mechanics follow in one compact sentence. The 'Not advice' fragment is short but borderline filler; overall there is little wasted text.

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 must convey what is returned, and it does enumerate the result dimensions (liquidity, slippage, impact curve, risk matrix). The payment handshake is also described well enough to execute, leaving only minor gaps about response formatting.

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 baseline is 3, and the description adds real meaning beyond the schema by explaining the payment parameter's gating behavior (call without payment for terms, sign, then call again with payment) rather than merely restating field types.

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 names concrete outputs (multi-size liquidity, sell slippage, AMM price impact curve, honeypot/exit risk matrix across USD tiers) that clearly separate it from sibling lookups like token_lookup or base_token_price. The framing is noun-heavy rather than an explicit verb, but an agent can still tell what it produces.

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?

It supplies a timing cue ('before trading') and a procedural sequence for payment, but never says when to prefer this over siblings such as exit_check, exit_check_bulk, or token_lookup, and offers no explicit exclusions.

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.