Skip to main content
Glama

fetchGithubReleases

Retrieve GitHub releases from the Goose repository to track version updates and changelog information for development monitoring.

Instructions

Fetch ALL GitHub releases from the Goose repo.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function that fetches GitHub releases from the block/goose repository using axios and maps the response data to ContentItem objects.
    async function fetchGithubReleases(): Promise<ContentItem[]> {
      const response = await axios.get(
        "https://api.github.com/repos/block/goose/releases",
        { headers: { Accept: "application/vnd.github+json" } }
      );
    
      return response.data.map((rel: any) => ({
        id: rel.tag_name,
        title: rel.name || rel.tag_name,
        url: rel.html_url,
        published_at: rel.published_at || rel.created_at,
        type: "release" as const,
      }));
    }
  • src/server.ts:159-164 (registration)
    Registration of the 'fetchGithubReleases' tool in the FastMCP server, specifying the name, description, input schema (empty object), and execution function that calls the handler and returns JSON string.
    server.addTool({
      name: "fetchGithubReleases",
      description: "Fetch ALL GitHub releases from the Goose repo.",
      parameters: z.object({}),
      execute: async () => JSON.stringify(await fetchGithubReleases()),
    });
  • TypeScript interface defining the structure of ContentItem objects returned by the tool, serving as the output schema.
    interface ContentItem {
      id: string;
      title: string;
      url: string;
      published_at: string;
      type: "video" | "blog" | "release";
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states 'Fetch ALL GitHub releases', which implies a read-only operation, but doesn't clarify aspects like rate limits, authentication needs, error handling, or what 'ALL' entails (e.g., pagination, date ranges). This leaves significant gaps in understanding how the tool behaves in practice.

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?

The description is a single, efficient sentence with no wasted words. It's front-loaded with the core action and resource, making it easy to parse quickly. Every part of the sentence contributes directly to understanding the tool's purpose.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is adequate but has clear gaps. It explains what the tool does but lacks behavioral details (e.g., how releases are returned, error cases). Without annotations or an output schema, the description should do more to cover these aspects for a complete understanding.

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?

The input schema has 0 parameters with 100% coverage, meaning no parameters are documented in the schema. The description doesn't add parameter details, which is appropriate since there are none to describe. This meets the baseline for tools with zero parameters, as there's nothing to compensate for.

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?

The description clearly states the action ('Fetch') and resource ('GitHub releases from the Goose repo'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'fetchGooseBlog' or 'fetchRss', which might also fetch content from different sources. The specificity about 'ALL' releases adds some distinction but not enough for full sibling differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives like 'fetchGooseBlog' or 'fetchRss'. It mentions 'ALL' releases, which implies completeness, but doesn't specify context, prerequisites, or exclusions. Without any usage instructions, the agent must infer when this tool is appropriate.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/EbonyLouis/content-fetcher-mcp2'

If you have feedback or need assistance with the MCP directory API, please join our Discord server