Skip to main content
Glama
pumpfun-claims-bot

pumpfun-claims-bot

by nirholas

get_creator_profile

Fetch a PumpFun creator profile by wallet address to review username, launch count, scam estimate, and recent coins for credibility checks before claims or token decisions.

Instructions

Fetch PumpFun creator profile — username, launch count, scam estimate, recent coins

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": {
      "wallet": "<wallet>"
    },
    "name": "get_creator_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
walletYesCreator wallet 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

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose the shape of the returned data, which is real value, and 'Fetch' implies a read-only lookup, but it says nothing about behavior for unknown/non-creator wallets, rate limits, or auth requirements.

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?

One sentence, front-loaded with the verb and resource, with the returned fields listed after the em dash. Nothing is wasted and nothing needs reordering.

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 tool with no output schema, enumerating the returned fields in the description is exactly the right compensation. The only gap is edge-case behavior when the wallet has no creator profile, which is minor.

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?

The single parameter has 100% schema description coverage ('Creator wallet address'), so the schema already does the work. The description adds no format, chain, or validation detail for the wallet argument beyond what the schema states, so the baseline 3 applies.

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 (Fetch) and a specific resource (PumpFun creator profile), then enumerates the fields returned (username, launch count, scam estimate, recent coins). That is enough to separate it from siblings like get_token_info or get_github_user, though it never explicitly contrasts itself 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?

Usage is only implied: an agent can infer this is the tool for creator-level data keyed on a wallet, but there is no explicit when-to-use, no statement of when to prefer get_token_info or get_token_holders instead, and no prerequisites or exclusions.

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