Skip to main content
Glama
github-fetcher

github-fetcher

by KurvCygnus

GitHub user stars

github_user_starred
Read-onlyIdempotent

List the repositories a GitHub user has starred, including when each star was given, with pagination for browsing through results.

Instructions

List the repositories a user has starred with the time each star was given; the star+json media type supplies starred_at. Costs 1 core call. Returns {items[{repo, stars, language, starred_at, pushed_at}], 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": {
      "user": "<user>"
    },
    "name": "github_user_starred"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, starting at 1
userYesGitHub user login, like octocat (alphanumerics and hyphens)
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

A3.5/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, open-world), and the description still adds real value: it discloses the rate-limit cost (1 core call) and the fact that starred_at depends on the star+json media type. It does not discuss the local cache that the 'fresh' parameter implies, which is the only notable omission.

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?

Three sentences, front-loaded with the purpose, then cost, then a compact return-shape sketch. Slightly dense with the brace-notation return signature, but every sentence carries information an agent needs.

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 inline return structure (items, page, per_page, has_more, next_page) usefully compensates. Rate-limit cost is disclosed. The gaps are minor: no note on what happens when a user has zero stars or on the cache-and-fresh interaction.

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 user, page, per_page, and fresh are already fully documented with ranges and formats. The description adds nothing about parameter behavior beyond what the schema says; its detail is about output, not inputs, so the baseline 3 is right.

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 and resource: list the repositories a given user has starred, including star timestamps. It is instantly distinguishable from github_user_repos in substance, though it never names the sibling it is closest to, so it falls just short of a 5.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no pointer to alternatives such as github_user_repos or github_repo. The purpose implies the use case, but the agent gets no routing help or exclusions from the description itself.

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