Skip to main content
Glama
github-fetcher

github-fetcher

by KurvCygnus

GitHub repository stargazers

github_stargazers
Read-onlyIdempotent

Retrieve a repository's stargazers with starred_at timestamps, ordered oldest-first across pages, to build a star timeline and compute star velocity client-side.

Instructions

List a repository's stargazers with the time each star was given (star+json media type). Pages are ordered oldest-first by default, so paged calls build a star timeline; compute velocity client-side from starred_at deltas. Costs 1 core call. Returns {items[{login, starred_at}], page, per_page, has_more, next_page}.

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, starting at 1
repoYesRepository in owner/name form
freshNoBypass the local cache
per_pageNoItems per page, 1-100, default 20

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 declare read-only, idempotent, open-world, non-destructive behavior, and the description adds traits annotations cannot express: the star+json media type requirement, the oldest-first ordering guarantee, the explicit cost of 1 core call, and the exact response envelope. These are the details an agent needs to plan a paged timeline and budget rate limit.

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?

Four short sentences, front-loaded with purpose then ordering, cost, and return shape; nothing is filler. The velocity-computation aside is advisory rather than definitional, which keeps it just short of maximal efficiency but still earns its place as usage guidance.

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 correctly supplies the return shape (items with login and starred_at plus paging fields) and pairs it with ordering, rate cost, and header/media-type context. Nothing needed to call a paginated stargazer listing correctly is missing.

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 parameters are already documented; the description goes beyond that by establishing that pages are ordered oldest-first, which is the fact that gives the page parameter meaning and determines how paging behaves. It does not restate per_page bounds, but no gap is left that the schema does not already close.

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 ("List a repository's stargazers") and immediately qualifies the payload with "the time each star was given", which separates it from contributor/branch/commit siblings that enumerate different relationship types. An agent can identify the resource and the distinguishing payload without opening the schema.

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 gives concrete usage context: paging builds a chronological star timeline and velocity should be computed client-side from starred_at deltas rather than looked up elsewhere. It stops short of naming an alternative tool or stating when not to use it, so it is strong context but not full when/when-not routing.

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