Skip to main content
Glama
github-fetcher

github-fetcher

by KurvCygnus

GitHub repository languages

github_languages
Read-onlyIdempotent

Read a GitHub repository's language breakdown as bytes per language, sorted descending, to identify which languages make up the codebase.

Instructions

Read a repository's language breakdown as bytes per language, sorted by bytes descending; byte counts come from GitHub's language statistics, so they measure code bytes rather than counting file extensions. Costs 1 core call. Returns {languages, total_bytes}.

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

Input Schema

NameRequiredDescriptionDefault
repoYesRepository in owner/name form
freshNoBypass the local cache

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

A3.8/5.0
Behavior4/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, so the bar is lower, and the description still adds real value: an explicit cost of 1 core call, a stated return shape {languages, total_bytes}, and the caveat that bytes reflect GitHub's computed code statistics rather than extension counting. It does not say what happens when a repository has no detected languages or how long the local cache persists, which keeps it out of the top band.

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 sentences, zero filler, and the operational definition of the resource is front-loaded ahead of the cost and return-shape details. Nothing repeats the schema or the annotations verbatim.

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 simple one-required-parameter read tool with no output schema, the description covers purpose, cost, return keys, and the meaning of the numbers, which is what an agent needs to call and interpret it. Minor gaps remain around empty/degenerate results and cache lifetime, but nothing essential 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 coverage is 100%, with both `repo` (owner/name) and `fresh` (bypass the local cache) documented in the schema itself, so the baseline of 3 applies. The description adds no parameter-specific detail beyond what the schema already states; its added meaning is about result semantics and cost, not the inputs.

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 ('Read a repository's language breakdown as bytes per language') and pins down semantics precisely: sorted by bytes descending, derived from GitHub language statistics rather than file extensions. It is unambiguous what the tool returns, but it never explicitly contrasts itself with adjacent siblings such as github_repo or github_tree, so sibling differentiation is left implicit.

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 rather than stated: it is evidently the tool for language composition, and the 'Costs 1 core call' note gives a budget-aware signal an agent can weigh against heavier calls. There is no when-to-use vs. alternative guidance, no mention of when the result would be the wrong choice (e.g. wanting per-file detail instead), and no precondition checks.

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