Skip to main content
Glama

token_pressure_lite

Read-onlyIdempotent

FREE lite buying-pressure + holder-health report for one Solana memecoin. Top-line only: net inflow needed for 2x, 5x and 10x moves, percent of sampled wallets in profit, total unrealized PnL headline, weighted average cost, MVRV and sample coverage. The full ladder (1.5x-100x), gross-of-fee figures, reserves, UPNL vs liquidity and per-holder detail are capped. Use it to triage whether a token deserves the full token_pressure report.

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_lite"
  }
}

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
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the description correctly spends its words on behavior the annotations cannot express: the output is deliberately truncated (2x/5x/10x only, gross-of-fee figures excluded, per-holder detail capped) and it is free. It does not mention sampling thresholds, rate limits, or failure modes, which keeps it just under 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the value proposition, then the enumerated outputs, then the usage rule — a sensible order with no filler sentences. The middle list of metrics is dense but each item earns its place by telling the agent what it will and will not get back.

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 carries the burden of describing return content and does so by enumerating the top-line metrics and explicitly listing what is capped. It does not describe the response's shape or how sample coverage should be interpreted, which is the main remaining gap for a report-style tool.

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% on the single required 'mint' parameter, including base58 format, length, an example, and an explicit rejection of EVM addresses. The description adds no meaning beyond that, 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?

The description names a specific verb+resource pair (buying-pressure + holder-health report for one Solana memecoin) and immediately qualifies it as the 'lite', top-line variant versus the full token_pressure report. An agent can distinguish it from its sibling without opening either 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?

It gives an explicit routing rule: 'Use it to triage whether a token deserves the full token_pressure report', naming the alternative and the condition that selects it. It stops short of stating the inverse (when to skip straight to token_pressure), so the guidance is clear but not fully bidirectional.

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.