Skip to main content
Glama

ArcanumFleet Pool Liquidity Check

arcanum_liquidity_check
Read-onlyIdempotent

Use this before swapping to check real-time DexScreener USD pool depth, 24h volume, price, and swap_ready (>= $15k liquidity) for a Solana mint. Costs 0.002 USDC via 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": {
      "mint": "<mint>"
    },
    "name": "arcanum_liquidity_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
mintYesBase58 Solana SPL token mint address

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / mint / description
      Previous value: -"Solana token mint address"New value: +"Base58 Solana SPL token mint address"
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world, so the safety profile is covered. The description adds genuinely non-obvious behavior: a 0.002 USDC x402 payment requirement and the concrete swap_ready threshold. It omits failure modes (invalid mint, unsupported pool, payment failure), 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?

One sentence, front-loaded with the usage trigger, then the returned signals, then the cost. Every clause carries information an agent needs; nothing is 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 no output schema, the description correctly enumerates the return fields (pool depth, volume, price, swap_ready) and discloses the paid-call cost, which is sufficient for a single-parameter read tool. Minor gaps remain around error/empty-pool responses and what swap_ready=false should lead the agent to do.

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 coverage is 100% and the single 'mint' parameter is fully documented as a Base58 SPL token mint address. The description only reinforces that the target is a Solana mint, adding no syntax, validation, or format detail beyond the schema, so the baseline 3 applies.

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 ('check real-time DexScreener USD pool depth, 24h volume, price, and swap_ready') scoped to 'a Solana mint'. It also encodes a decision rule (swap_ready >= $15k liquidity), which no sibling (e.g. arcanum_jupiter_quote) provides, so an agent can distinguish it without opening a schema.

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

Usage Guidelines4/5

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

'Use this before swapping' gives a clear triggering context for invocation. It stops short of naming an alternative or stating when not to use it (e.g. when a quote alone suffices), so it is strong but not exhaustive.

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