Skip to main content
Glama

get-github-user

Fetches public profile information for a given GitHub username so you can look up account details.

Instructions

Fetches public profile information for a GitHub user

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": {
      "username": "<username>"
    },
    "name": "get-github-user"
  }
}

Input Schema

NameRequiredDescriptionDefault
usernameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden, yet it discloses almost nothing beyond the surface intent. It hints that only public data is returned but says nothing about authentication requirements, rate limits, or behavior for a nonexistent or renamed user.

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?

A single short sentence with the verb and object front-loaded and no wasted words. It is efficient, though its brevity borders on thin for a tool with no annotations.

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?

The tool is simple (one required parameter, no nesting, no output schema), so the description is close to sufficient for correct invocation. However, for a tool with zero annotation coverage it should say more about auth, rate limits, and what 'public profile information' actually encompasses.

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 0%, so the description must compensate for the single 'username' parameter. Saying 'for a GitHub user' implies the value is a GitHub login rather than an email or ID, which is a small but real addition beyond the bare string type.

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 ('Fetches') and resource ('public profile information for a GitHub user'), which is unambiguous. It does not need to differentiate from siblings, since none of the listed tools touch GitHub, but it also gives no explicit contrast.

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 guidance on when to use this versus alternatives, when not to use it, or what preconditions apply. The only usage signal is the word 'public', leaving the agent to infer the rest.

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