Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

github_user

Fetch public GitHub user details from a username, handle, or profile URL to identify an account and access its profile information.

Instructions

github: User. GET /v1/github/user. Provide one of: handle, url. Get public GitHub user details for a user. Pass username, handle, or url. Costs 1 credit when it succeeds. Errors, blocked or timed-out requests, invalid requests and cache hits cost nothing. A not-found or empty result is charged only where that operation's published cost says so.

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

Input Schema

NameRequiredDescriptionDefault
urlNoGitHub user URL, e.g. https://github.com/torvalds.
handleNoGitHub username/handle of the user you want the details for

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does deliver the most important behavioral fact for this API: a 1-credit charge on success, with errors, blocked/timed-out requests, invalid requests, and cache hits free. It stops short of describing auth requirements, rate limits, or what the response contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The cost model is front-loaded and useful, but "Provide one of: handle, url" and "Pass username, handle, or url" are redundant restatements of the same rule, and "github: User. GET /v1/github/user." is internal API metadata that does little for an agent.

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 simple two-optional-parameter read tool with full schema coverage and no output schema, the definition covers purpose, input selection, and billing behavior adequately. The main gap is that it never hints at what the returned user details include.

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 the schema already defines both handle and url, giving a baseline of 3. The description only restates the same choice and even introduces a third name, "username," that is not a schema property, which adds mild confusion rather than meaning.

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 and resource: "Get public GitHub user details for a user," plus the concrete route GET /v1/github/user. It is clearly a single-user profile lookup rather than the activity, followers, or repositories siblings, though it never names a sibling to contrast against.

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?

"Provide one of: handle, url" establishes an either/or input constraint, which is a real usage rule, but there is no guidance on when to choose this tool over github_user_repositories or github_user_activity, and no when-not conditions.

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

Deploy Server

Other Tools