Skip to main content
Glama

token_pressure

Read-onlyIdempotent

Full buying-pressure + holder-health report for ONE Solana memecoin (mint address in). BUYING PRESSURE: deterministic constant-product math on live pool reserves — the exact net quote inflow that moves the price to 1.5x, 2x, 3x, 5x, 10x, 25x, 50x and 100x, with target prices and target market caps, plus the gross inflow after the venue fee. Works for pump.fun bonding curves (virtual reserves read from the curve account, pre-graduation), PumpSwap and Raydium constant-product pools; concentrated pools (CLMM/DLMM) are reported unavailable with the reason, never approximated. HOLDER HEALTH: cost basis reconstructed from public chain history over a bounded top-holder sample (pool vaults excluded) — total unrealized PnL, percent of sampled wallets in profit, supply-weighted average cost, MVRV, UPNL vs liquidity, per-holder detail, and the sample coverage (% of supply) stated up front. Includes a canonical-contract check for tracked narratives (NEET at launch): clones trading on the name are flagged and the real contract named. Every report carries its methodology (pool type, reserves snapshot slot, fee assumption, holder sample bounds) and names its data gaps — figures that cannot be computed from public state are reported unavailable, never estimated. Cost: $0.02 USDC per call via x402 (Base settlement; Solana settlement when configured) — no API key needed. Use it to answer 'how much money has to arrive for this to 2x / 10x, and are the holders sitting on profit or underwater?' before sizing into any Solana memecoin.

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

Input Schema

NameRequiredDescriptionDefault
mintYesSolana token mint address (base58, 32-44 chars), e.g. Ce2gx9KGXJ6C9Mp5b5x1sn9Mg87JwEbrQby4Zqo3pump. EVM 0x addresses are rejected — this is a Solana tool.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive, and the description still adds substantial behavior: a $0.02 USDC x402 charge per call with no API key, deterministic constant-product math, explicit refusal to approximate concentrated pools, and a policy of reporting unavailable rather than estimating. It also discloses that every report carries methodology (pool type, snapshot slot, fee assumption, sample bounds) and names its data gaps.

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?

Purpose and scope are front-loaded, and the caps-style section labels (BUYING PRESSURE, HOLDER HEALTH) make a dense block scannable. It is long and the 1.5x-through-100x enumeration plus the full holder-metric list is verbose, but almost every clause conveys actionable capability rather than filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description compensates by describing the return payload in detail: target prices, target market caps, gross inflow after venue fee, sample coverage percentage, per-holder detail, and canonical-contract checks. Payment mechanics, failure modes (CLMM/DLMM unavailable), and data-gap policy are all covered, leaving nothing an agent needs before calling.

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 param description already specifies base58 format, length, an example, and rejection of EVM addresses. The description only reinforces the single-mint scope ('ONE Solana memecoin') without adding format or validation detail. With the schema doing the work, 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 opens with a specific verb-and-resource statement: a 'Full buying-pressure + holder-health report for ONE Solana memecoin (mint address in)', and then enumerates the concrete outputs (target inflows to 1.5x–100x, MVRV, UPNL vs liquidity). An agent can tell exactly what it produces. It never names the sibling token_pressure_lite, so the 'Full' qualifier hints at a lighter variant without disambiguating it.

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?

It supplies a clear context-of-use framing: answer 'how much money has to arrive for this to 2x / 10x, and are the holders sitting on profit or underwater?' before sizing into a memecoin. That is genuine when-to-use guidance. It stops short of explicit when-not conditions or routing to the lite sibling.

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.