Skip to main content
Glama

A GitHub user's public profile and their five most-starred

github_user
Read-only

A GitHub user's public profile (name, company, location, blog, bio, followers, public repos, creation date) and their five most-starred repositories that are not forks. Related tools on this server, for a different need: github_repo when you need a public GitHub repository: stars, forks, watchers, open; github_issues when you need to search a GitHub repository's issues or pull requests. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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 login

Output Schema

NameRequiredDescriptionDefault
bioNo
urlNo
blogNo
nameNo
loginNo
sourceNo
companyNo
locationNo
topReposNo
checkedAtNo
createdAtNo
followersNo
publicReposNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds genuinely new behavioral context: cost is $0.002 per successful call via x402 (USDC on Base, Solana and 10+ networks) and failed calls are not charged, which an agent must know before invoking. It does not discuss rate limits or how the five-repo selection is ordered/tied, leaving a minor gap.

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?

Front-loaded with what the tool returns, followed by routing and pricing in descending order of importance. Sentences are dense but purposeful; the payment-network enumeration ('Solana and 10 more networks') is slightly padded detail but still informative.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, yet the description still summarizes the returned fields, and it covers cost, scope, and alternatives. For a one-parameter read-only lookup tool, nothing an agent needs in order to invoke it correctly is missing.

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?

There is a single parameter, 'user', with 100% schema description coverage ('GitHub login'), so the schema carries the semantics. The description restates that the tool operates on a GitHub user but adds no extra detail such as case sensitivity, org-account behavior, or 404 handling for unknown logins. Baseline 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?

States precisely what is returned: a user's public profile fields (name, company, location, blog, bio, followers, public repos, creation date) plus their five most-starred non-fork repos. It immediately distinguishes itself from github_repo and github_issues by naming what those siblings cover instead.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit routing is given for both named alternatives: github_repo for repository stats, github_issues for issue/PR search. The 'not forks' qualifier also signals a scoping choice to the caller. It lacks an explicit 'when to use this instead' framing and covers only two of many siblings, so it is clear but not exhaustive.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources