Skip to main content
Glama
github-fetcher

github-fetcher

by KurvCygnus

GitHub user profile

github_user
Read-onlyIdempotent

Retrieve a GitHub user's profile by login, including name, bio, company, location, public repository count, and follower counts. Returns structured user data.

Instructions

Read a GitHub user's profile: name, type, bio, company, location, blog, public repository count, and follower counts. Costs 1 core call. Returns {login, name, type, bio, company, location, blog, public_repos, followers, following, created_at, html_url}.

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": {
      "user": "<user>"
    },
    "name": "github_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
userYesGitHub user login, like octocat (alphanumerics and hyphens)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds real context beyond that: the 'Costs 1 core call' budget note and the explicit return field list. It stops short of describing failure modes such as a 404 or rate-limit behavior, which keeps it below a 5.

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?

Two sentences, both front-loaded with the most useful information: purpose first, then cost and return shape. No filler, no redundancy, and the return field list is compact enough to scan.

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?

There is no output schema, but the description compensates by enumerating the returned fields, which is exactly what an agent needs to decide whether to call this tool. The remaining gap is behavioral: no note on what happens for an invalid or deleted login, which matters for an open-world API call.

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 description coverage is 100% and the single `user` parameter already documents the login format with an example ('octocat'). The description adds no meaning beyond the schema, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource ('Read a GitHub user's profile') and enumerates the fields returned (name, type, bio, company, location, blog, public_repos, followers). That distinguishes it clearly from sibling tools like github_user_repos or github_search_users, which cover different resources.

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 implied by the verb and resource, but there is no explicit when-to-use statement, no exclusion of alternatives (e.g., github_search_users when the login is unknown), and no mention of error behavior for a nonexistent user. An agent can infer the case but is given no routing guidance.

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