Skip to main content
Glama
pumpfun-claims-bot

pumpfun-claims-bot

by nirholas

get_github_user

Fetch a GitHub user profile by username or numeric ID to retrieve repos, followers, bio, and account age for identity and credibility checks.

Instructions

Fetch GitHub user profile by username or numeric ID — repos, followers, bio, account age

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

Input Schema

NameRequiredDescriptionDefault
userIdNoGitHub numeric user ID
usernameNoGitHub username (login)

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.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It implies a read-only lookup but says nothing about authentication requirements, rate limits, not-found/error behavior, or whether the two identifiers can be combined — all material for a GitHub API call.

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 front-loaded sentence with no filler; the resource and scope appear before the enumerated return fields. Nothing in it is redundant.

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 simple two-parameter read tool with a fully described schema and no output schema, the description covers the core purpose. It leaves gaps on identifier precedence and on failure/auth behavior, which an agent would want before calling.

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?

Schema coverage is 100%, so both parameters are already documented in the schema; that sets the baseline at 3. The phrase "by username or numeric ID" adds a small amount of meaning by presenting the two parameters as interchangeable identifiers, but gives no precedence rule.

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?

"Fetch GitHub user profile by username or numeric ID" states a specific verb and resource, and the trailing clause names the returned fields (repos, followers, bio, account age). It is clearly distinguishable from the unrelated siblings (token, pool, claim tools), though it does not explicitly differentiate itself from anything.

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 when-to-use guidance, no exclusions, and no named alternative. Critically, both parameters are optional and the description never says what happens if neither is supplied, or how the tool chooses between username and numeric ID when both are passed.

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