github-fetcher

GitHub release

github_release

Read-onlyIdempotent

Retrieve GitHub release details by tag or latest, including assets and download URLs, to provide AI agents with version-specific release data.

Instructions

Read the latest release or the release for a specific tag, including assets and download URLs.

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

Input Schema

Name	Required	Description
`tag`	No	Release tag; omit for the latest release
`repo`	Yes	Repository in owner/name form
`fresh`	No	Bypass the local cache

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 1, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds what is returned (assets and download URLs), which is useful, but says nothing about the caching behavior surfaced by the 'fresh' parameter or about rate limiting, which matters for an openWorld tool.

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?

A single front-loaded sentence with no filler; the access-mode distinction comes first and the return content trails it efficiently.

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 usefully names the return payload (assets and download URLs), and the read-only annotations cover safety. Only the cache/rate-limit behavior is left implicit, a minor gap for a simple read tool.

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%, so all three parameters including 'tag' and 'fresh' are already documented. The description's mention of 'a specific tag' merely echoes the schema and adds no format or edge-case detail. Baseline 3 applies when the schema carries the load.

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?

States a specific verb (Read) and resource (release) with the two access modes (latest vs. specific tag). It does not, however, distinguish itself from the sibling github_releases, which an agent must guess is the list-oriented counterpart.

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?

The description implies when to use it (fetch the latest or a tagged release) but gives no explicit when-not guidance or pointer to github_releases for enumeration. The choice between this and a list tool is left to inference.

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