Skip to main content
Glama
github-fetcher

github-fetcher

by KurvCygnus

GitHub repository activity

github_repo_activity
Read-onlyIdempotent

Measure how alive a GitHub repository is over a set window: pull requests opened, merged and closed, median merge hours, issues, commits, active contributors and releases.

Instructions

Answer how alive a repository has been over a window, from core endpoints only: pulls opened/merged/closed (closed counts PRs closed without merging) with bot-authored opens and the median hours from opening to merge, issues opened and closed, the window's commit total, active contributors, and the release count. Pulls and issues walk newest-first until the window edge (10-page cap), releases cap at 3 pages; a *_truncated flag reports a walk the cap stopped, and stats GitHub is still computing report null commits/contributors with stats_unavailable. Costs 4-12 core calls, none search. Returns {repo, window_days, generated_at, pulls, median_merge_hours, issues, commits, active_contributors, releases, pulls_truncated, issues_truncated, releases_truncated, stats_unavailable}.

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": {
      "repo": "<repo>"
    },
    "name": "github_repo_activity"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoYesRepository in owner/name form
freshNoBypass the local cache
window_daysNoAnalysis window in days, 1-365, default 30

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description layers on substantial extra context: pagination caps per resource type, *_truncated flags, null commits/contributors with stats_unavailable when GitHub is still computing, and an explicit 4-12 core-call cost. This is exactly the kind of behavior an agent needs before invoking and interpreting results.

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?

The description is dense but front-loaded: purpose first, then measurement details, then pagination/cost caveats, then the return shape. Nearly every clause carries information, though the single long paragraph and the enumerated return-field list make it slightly heavy to scan.

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 compensates by listing the full return object keys and explaining the meaning of the truncation and stats_unavailable fields. Combined with the cost and pagination notes, an agent has everything needed to call it and interpret the response.

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 adds real meaning: it explains that the window defines a walk edge, that pulls/issues walk newest-first with a 10-page cap and releases cap at 3 pages, and that truncation flags report a capped walk. This clarifies the behavioral consequence of window_days beyond the schema's '1-365, default 30'. The 'fresh' cache-bypass parameter is not elaborated, keeping it from a 5.

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?

The description opens with a specific verb+resource framing ('Answer how alive a repository has been over a window') and enumerates exactly what is measured: PRs opened/merged/closed, median merge hours, issues, commits, contributors, releases. It is clearly distinguishable from single-resource siblings like github_prs or github_commits, though it never names the closest-sounding sibling (github_repo_health) to draw the line explicitly.

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?

'From core endpoints only' and 'Costs 4-12 core calls, none search' implicitly steer the agent away from search-based tools and signal the cost profile, which is useful selection context. However, there is no explicit when-to-use/when-not statement or named alternative, so the guidance remains 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.