Skip to main content
Glama

A public GitHub repository: stars, forks, watchers, open

github_repo
Read-only

A public GitHub repository: stars, forks, watchers, open issues and pull requests, license, default branch, created and pushed dates, topics, languages with shares, latest release, commits in the last four weeks and the top five contributors. Up to six GitHub requests per call. Commit statistics are null while GitHub computes them. Source: GitHub REST API. Related tools on this server, for a different need: github_issues when you need to search a GitHub repository's issues or pull requests; github_releases when you need to list a GitHub repository's latest releases. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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

Input Schema

NameRequiredDescriptionDefault
repoYesowner/name, e.g. cloudflare/workers-sdk, or a github.com URL

Output Schema

NameRequiredDescriptionDefault
urlNo
forkNo
repoNo
forksNo
starsNo
sourceNo
topicsNo
licenseNo
archivedNo
pushedAtNo
watchersNo
checkedAtNo
createdAtNo
languagesNo
openIssuesNo
descriptionNo
contributorsNo
defaultBranchNo
latestReleaseNo
primaryLanguageNo
openPullRequestsNo
commitsLast4WeeksNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "archived": {},
      +    "checkedAt": {},
      +    "commitsLast4Weeks": {},
      +    "contributors": {},
      +    "createdAt": {},
      +    "defaultBranch": {},
      +    "description": {},
      +    "fork": {},
      +    "forks": {},
      +    "languages": {},
      +    "latestRelease": {},
      +    "license": {},
      +    "openIssues": {},
      +    "openPullRequests": {},
      +    "primaryLanguage": {},
      +    "pushedAt": {},
      +    "repo": {},
      +    "source": {},
      +    "stars": {},
      +    "topics": {},
      +    "url": {},
      +    "watchers": {}
      +  },
      +  "type": "object"
      +}
  2. Added

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds substantial context beyond them: a per-call request budget ("Up to six GitHub requests per call"), a data caveat ("Commit statistics are null while GitHub computes them"), the upstream source (GitHub REST API), and the pricing/billing failure behavior. These are exactly the traits an agent cannot get from structured fields and that affect whether a call is worth making.

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?

Content is front-loaded with the field inventory, followed by caveats, alternatives, and pricing in a logical order. The field enumeration is long but each item is a real return-value hint; the only mild waste is the pricing/network detail, which is longer than the decision value it provides.

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 single-parameter, read-only lookup with an output schema, the definition covers the data surface, upstream rate structure, a known null-value caveat, and sibling routing — enough to call it correctly. Minor gaps: no statement about behavior when the repo does not exist or is private, and no hint about pagination or contributor/release truncation beyond the top-five note.

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?

There is a single required parameter at 100% schema coverage, and the schema already documents the "owner/name or github.com URL" format with an example. The description adds no further meaning about the repo parameter (e.g. case sensitivity, whether renaming/redirects resolve). Baseline 3 applies since the schema carries the burden.

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 opening sentence enumerates precisely what the resource contains (stars, forks, watchers, issues, license, default branch, topics, languages, latest release, commit activity, contributors), which is far more specific than the title alone. It also explicitly separates itself from github_issues and github_releases. The only shortfall is that there is no operative verb ("fetch/retrieve") — it reads as a resource definition rather than an action, though the intent is unambiguous.

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

Usage Guidelines4/5

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

It routes the agent to alternatives with explicit conditions: github_issues "when you need to search a GitHub repository's issues or pull requests" and github_releases "when you need to list ... latest releases." That is genuine when-to-use guidance for the siblings, but there is no explicit statement of when to choose this tool or any exclusion/prerequisite (e.g. auth, private repos).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources