Skip to main content
Glama

Solana PumpFun Paywall

pump_koth_scan

Scan active Pump.fun curves approaching King of the Hill (0.005 SOL)

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. 'Scan' implies a non-mutating read and the 0.005 SOL threshold defines the inclusion criteria, which is useful behavioral context, but it says nothing about what is returned (list contents, ordering, result count), whether it hits rate limits, or which network/state is queried.

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?

A single sentence with the qualifying threshold front-loaded alongside the action. Nothing is wasted and there is no hedging or filler.

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

Completeness3/5

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

For a zero-parameter scan with no output schema and no annotations, the definition should at least sketch the shape of the result set. It defines the filter precisely but leaves the return value entirely to inference, which is the main remaining gap.

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 zero parameters, so there is nothing for the description to disambiguate; the schema is trivially complete. Baseline 4 applies for a parameterless tool.

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?

States a specific verb ('Scan') plus a specific resource ('active Pump.fun curves') and a quantifiable criterion ('approaching King of the Hill (0.005 SOL)'), which is enough to distinguish it from siblings like pump_bonding_curve or pump_rug_check. It stops short of explicitly naming how it differs from those siblings, so it is clear but not fully differentiated.

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 phrase 'approaching King of the Hill' implies the use case (finding tokens near migration/threshold), but there is no explicit when-to-use, when-not-to-use, or pointer to an alternative tool. An agent must infer the trigger condition rather than being told it.

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