Skip to main content
Glama
github-fetcher

github-fetcher

by KurvCygnus

GitHub user health

github_user_health
Read-onlyIdempotent

Audit a GitHub user's profile in one call: original vs fork split, star totals, top repositories, language distribution, and 90-day push activity.

Instructions

One-call user profile audit: original vs fork split, star totals, top repositories, language distribution, and 90-day push activity — the multi-call walk of a manual audit, compressed to 1. Costs 2-11 core calls, none search. top_repos, languages, and 90-day push activity exclude forks by default (include_forks: true keeps them); originals, forks, fork_share, and total_stars always count them. Returns {user, name, type, public_repos, originals, forks, fork_share, total_stars, top_repos[{full_name, stars, language, pushed_at}], languages, recent_pushes_90d, oldest_push_90d_gap_days, repos_truncated, meta}.

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_health"
  }
}

Input Schema

NameRequiredDescriptionDefault
userYesGitHub user login, like octocat (alphanumerics and hyphens)
freshNoBypass the local cache
per_pageNoAccepted for symmetry with the user tools; the metrics walk always reads 100 repositories per page (the gather's fixed page size)
include_forksNoInclude fork repositories in the top_repos, languages, and push-activity metrics; defaults to false, pass true to include them

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.5.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, openWorld), yet the description adds real behavioral context beyond them: API call cost and budget impact, the default fork-exclusion rule for three specific metrics, and the counter-rule that originals/forks/fork_share/total_stars always count forks. That defaulting nuance is the kind of trap an agent would otherwise get wrong.

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 the value proposition, then cost, then the fork-default rule, then the return shape — a sensible ordering with little filler. The inline field list in the return shape is dense but justified because there is no output schema; only minor tightening is possible.

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?

With no output schema, the description takes on return-value disclosure and does so fully, listing every top-level field including meta and repos_truncated. Combined with the cost and fork-semantics notes, an agent has everything needed to decide, call, and interpret the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description earns extra credit by clarifying which metrics respond to include_forks and which are fork-invariant — a distinction the schema only states one-sidedly. It adds nothing about fresh or per_page (the per_page no-op note lives only in the schema), so it is not exhaustive.

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+resource framing ('One-call user profile audit') and enumerates exactly what the audit contains: original vs fork split, star totals, top repositories, language distribution, and 90-day push activity. The phrase 'the multi-call walk of a manual audit, compressed to 1' makes it distinguishable from the granular siblings like github_user_repos or github_user_events without needing their schemas.

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?

It clearly positions itself as a replacement for a multi-call manual audit and quantifies the cost ('2-11 core calls, none search'), which lets an agent weigh it against chaining github_user + github_user_repos + github_languages. It does not explicitly state when NOT to use it (e.g., when only a single field like starred repos is needed), so the exclusion side is implied rather than stated.

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