Skip to main content
Glama

Volume alert

volume_alert
Read-only

Find Solana tokens with unusual volume spikes right now. Returns tokens where recent 1h volume is disproportionately high vs 24h average — early signal for pumps. Costs $0.002 USDC per call.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "volume_alert"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Adds real value beyond the readOnly/openWorld annotations: it discloses the detection logic (1h vs 24h volume ratio), that it is a real-time snapshot, and the $0.002 per-call cost, which is important for an agent managing spend. It lacks return shape detail and limits/pagination, but for a zero-parameter scan that is a minor gap.

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?

Three tight sentences: purpose and scope first, mechanics second, cost last. Every sentence carries information an agent needs, and the most decision-relevant content is front-loaded.

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 does the necessary work of explaining what is returned (tokens with outsized 1h volume) and the cost of a call. It falls short only on result size, ordering, and whether any paging or cap applies.

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?

The tool takes no parameters, so the baseline of 4 applies. There is nothing for the description to compensate for, and it correctly avoids inventing implicit filters.

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?

Specific verb (Find) plus specific resource (Solana tokens) plus a precise criterion (1h volume disproportionately high vs 24h average). This implicitly separates it from siblings like trending_tokens, new_pairs, and whale_alert, but it never explicitly contrasts with any of them.

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 phrasing 'right now' and 'early signal for pumps' implies the use case, giving an agent a reasonable idea of intent. However, there is no explicit when-to-use/when-not guidance and no named alternative for related token-discovery questions.

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