Skip to main content
Glama

Volume check

volume_check

PAYWALLED. Is a token's volume real demand? Round-trip analysis of the last 24h: how much volume came from wallets buying and selling the same token back and forth (wash trading, arbitrage or market making) versus one-way trades, with the top round-trippers and pool liquidity. Returns x402 payment instructions for GET /api/x402/volume-check/{mint} ($0.004).

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

Input Schema

NameRequiredDescriptionDefault
mintYesToken mint address on X1.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/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 cost ($0.004), the endpoint, and critically that the call returns x402 payment instructions rather than the data itself — a non-obvious two-step flow an agent would otherwise trip over. It also states the analysis window (24h) and what the underlying payload contains, though it says nothing about rate limits or what happens after payment.

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-relevant question, followed by what the analysis measures and then the commercial terms. Three sentences with little waste, though 'Round-trip analysis of the last 24h' and the following clause partially restate each other.

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, no-annotation tool, the description supplies what an agent needs: what is computed, over what window, that it is paid, the price, and that the immediate return is payment instructions. Only the post-payment result format and any limits are left unspecified.

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% and the single parameter is documented as 'Token mint address on X1.' The description adds marginal value by showing the mint is substituted into the GET /api/x402/volume-check/{mint} path, but otherwise repeats the schema's job. Baseline 3 applies.

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 specific analysis and resource: round-trip volume analysis of the last 24h for a token, splitting wallets buying and selling the same token from one-way trades. That is far more specific than a generic 'token volume' tool and is distinguishable from siblings like arc_trades or recent_trades, though it never names an alternative explicitly.

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 framing question 'Is a token's volume real demand?' implies the use case (screening for wash trading before trusting volume), and 'PAYWALLED' plus the $0.004 price signal a paid tool. However, there is no explicit when-to-use/when-not-to-use statement and no routing to a cheaper sibling such as arc_token_check or arc_trades for a quick read.

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