Skip to main content
Glama
pumpfun-claims-bot

pumpfun-claims-bot

by nirholas

get_token_info

Fetch PumpFun token metadata, market cap, bonding curve progress, and flags by mint address to assess token status and graduation potential.

Instructions

Fetch PumpFun token metadata, market cap, bonding curve progress, and flags

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

Input Schema

NameRequiredDescriptionDefault
mintYesToken mint address

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.5
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv1.0.4

TDQS

B3.2/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: 'Fetch' implies a read-only operation and the field list tells the agent roughly what data is returned. It does not say what happens for an unknown/non-PumpFun mint, whether results are cached or rate-limited, or whether 'flags' means risk indicators.

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?

A single front-loaded sentence with no filler, and the resource and returned fields come first. The comma-separated data list is slightly dense ('flags' is unexplained) but nothing is wasted.

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 one-parameter read tool with no output schema, the description gives a partial return-value outline (metadata, market cap, bonding curve progress, flags), which is the minimum needed. It leaves gaps on return structure, the meaning of 'flags', and error behavior for invalid mints.

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?

Only one parameter exists and the schema fully documents it as the token mint address, so the baseline is 3. The description adds nothing about the mint beyond confirming that a token is identified, which the schema already does.

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?

Uses a specific verb (Fetch) with a specific resource (PumpFun token metadata) and enumerates what comes back: market cap, bonding curve progress, and flags. That makes it clearly distinct from siblings like get_token_holders or get_token_trades, though it never names those siblings as alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to use this tool versus the other token-related siblings, no prerequisite that the mint must exist on PumpFun, and no exclusion of cases where a different tool is better. The agent must infer usage entirely from the name and the listed fields.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.