Skip to main content
Glama
github-fetcher

github-fetcher

by KurvCygnus

GitHub repository batch

github_repos
Read-onlyIdempotent

Fetch details for up to 20 GitHub repositories in one batch, returning per-repository success or error data so one missing or inaccessible repo does not fail the whole request.

Instructions

Batch repository lookup: fetches up to 20 repositories concurrently, one core call each, and reports per-item success and failure so one missing or inaccessible repo never rejects the call. Returns {results[{repo, ok, data{full_name, description, private, visibility, fork, stars, forks, language, pushed_at, default_branch}} or {repo, ok, error{code, message}}], elapsed_ms}.

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": {
      "repos": "<repos>"
    },
    "name": "github_repos"
  }
}

Input Schema

NameRequiredDescriptionDefault
freshNoBypass the local cache
reposYesRepositories in owner/name form

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

A3.9/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, open-world), yet the description adds real operational context beyond them: the 20-item concurrency cap, the rate-limit cost ('one core call each'), and the per-item error-isolation contract so one inaccessible repo never rejects the call. It also spells out the response envelope because no output schema exists, leaving little behavioral ambiguity.

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?

Two sentences, front-loaded with the purpose and capped by a compact return-shape notation that earns its place given the absence of an output schema. The type expression is dense but not padded; no sentence is filler.

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?

For a read-only batch fetcher with no output schema, the description supplies the essentials: item cap, concurrency model, error isolation, and response fields. It stops short of noting authentication requirements for private repositories or how caching interacts with 'fresh', which are the remaining gaps.

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 both 'repos' (owner/name form, 1-20 items) and 'fresh' (bypass local cache) are already documented. The description's 'up to 20 repositories' merely restates maxItems and adds no new meaning for either parameter, so the baseline 3 applies.

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?

Names a specific verb and resource ('Batch repository lookup') and pins down scope precisely: up to 20 repos, fetched concurrently, one core call each. That contrasts with the single-repo sibling github_repo by implication, but no sibling is named explicitly, so differentiation relies on the word 'Batch' rather than a direct pointer.

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 context is implied by the batch limit and by the partial-failure guarantee (use this when some repos may be missing or inaccessible). There is no explicit when-to-use/when-not statement, no guidance on when to pick github_repo or github_search_repos instead, and no advice on when the 'fresh' cache flag matters.

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