Skip to main content
Glama
pumpfun-claims-bot

pumpfun-claims-bot

by nirholas

get_claim_history

Check a GitHub user's claim history to determine whether they have claimed, count their claims, and identify which token mints they claimed from.

Instructions

Check claim history for a GitHub user — whether they have claimed, claim count, and which token mints they claimed from

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": {
      "githubUserId": "<githubUserId>"
    },
    "name": "get_claim_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
githubUserIdYesGitHub numeric user ID

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

A3.5/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It usefully discloses what the result contains (claimed flag, count, mints), which stands in for a missing output schema, but says nothing about behavior for unknown users, empty histories, authentication needs, or rate limits.

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?

One compact sentence, front-loaded with the action and resource, with the em-dash list of returned fields appended efficiently. Nothing is wasted, though the enumerated return fields arguably belong in an output schema rather than the description.

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?

For a one-parameter read lookup with no annotations and no output schema, the description covers both what it queries and what comes back. The main residual gap is edge-case behavior (user with no claims, invalid ID), which is minor at this complexity level.

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?

There is a single parameter with 100% schema coverage, and the schema already explains it is a GitHub numeric user ID. The description's "for a GitHub user" merely restates that, adding no format, sourcing, or lookup guidance.

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 gives a specific verb and resource ("Check claim history for a GitHub user") and enumerates the returned facts: claimed status, claim count, and source token mints. That is enough to distinguish it from profile-style siblings like get_github_user or get_creator_profile, though no sibling is named explicitly.

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?

Usage is only implied by the phrase "for a GitHub user" — an agent can infer this is a per-user lookup, but there is no statement of when to prefer it over get_github_user or other user-oriented tools, and no prerequisites or exclusions are given.

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