Skip to main content
Glama
github-fetcher

github-fetcher

by KurvCygnus

GitHub repository contributors

github_contributors
Read-onlyIdempotent

Retrieve a repository's contributors with login, account type, and contribution counts for a given owner/name repo. Supports pagination and cache bypass; anonymous contributors are excluded.

Instructions

List a repository's contributors with login, account type, and contribution count; anonymous contributors are never included. Costs 1 core call. Returns {items[{login, type, contributions}], 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_contributors"
  }
}

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.3.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuinely new context: anonymous contributors are excluded from results and the call costs 1 core call against the rate limit, plus the exact response envelope including pagination fields. It stops short of describing ordering or what happens on a nonexistent repo.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two dense sentences, front-loaded with the resource and returned fields, followed by cost and response shape. No filler, no restatement of the tool name.

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

Completeness4/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 spelling out the return envelope and pagination contract, which is what an agent needs to iterate pages. Minor gaps remain: no mention of result ordering or behavior when the repo has no contributors, but nothing essential to a correct call 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?

Schema description coverage is 100%, so all four parameters (repo, page, per_page, fresh) are already documented in the schema, including per_page bounds and defaults. The description adds nothing parameter-specific beyond echoing page/per_page in the response shape, so the 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 a specific verb and resource ('List a repository's contributors') and names the exact fields returned (login, account type, contribution count). No sibling tool covers contributor listing, so an agent can route here without ambiguity.

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?

Usage is implied by the resource name — fetch contributors for a given repo — but there is no explicit when-to-use, when-not-to-use, or comparison to an alternative such as github_user_repos or github_repo. The only stated exclusion concerns anonymous contributors, which is a data behavior rather than tool-selection guidance.

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