Skip to main content
Glama

get_repository

Read-only

Fetch metadata for a single GitHub repository, including description, language, stars, forks, default branch, license, topics, and dates; not for issues or pull requests.

Instructions

Get metadata for ONE repository: description, primary language, stars, forks, watchers, default branch, license, topics, created/last-pushed dates. Do NOT use to count or list issues (its open_issues_and_prs mixes issues with pull requests; use list_open_issues), for pull requests (use list_pull_requests), or to see who changed what (use get_recent_commits).

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": "get_repository"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoYesRepository as 'owner/name' (e.g. 'octocat/hello-world'). A bare name like 'hello-world' is resolved against the authenticated user's account.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds the substantive disclosure that the returned open_issues_and_prs field is semantically mixed and should not be trusted as an issue count. With no output schema, the field enumeration does real work in describing the response. It stops short of stating anything about auth scope for private repos or rate limits, which is a live concern for an openWorld read 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?

Two sentences, both front-loaded: the capability and returned fields come first, the routing rules second. Every clause carries information — no restatement of the name, no filler, and the parenthetical explanation of the mixed field is worth its length.

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

Completeness5/5

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

For a one-parameter read tool with no output schema, the description fully shoulders the burden: it names the return fields and flags the one field whose name is misleading. Nothing an agent needs in order to pick this tool and interpret the result 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 description coverage is 100% and the single parameter is fully documented in-schema, including the 'owner/name' format and bare-name resolution against the authenticated user. The description contributes nothing about the repo argument, so it earns the baseline 3 rather than credit for added meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb and resource scoped to exactly one repository ('Get metadata for ONE repository') and enumerates the fields returned (description, language, stars, forks, default branch, license, topics, dates). The capitalized 'ONE' and the follow-on exclusions make it immediately distinguishable from list- and search-style siblings.

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

Usage Guidelines5/5

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

Gives three explicit when-not-to-use rules, each paired with the correct alternative: issues via list_open_issues, PRs via list_pull_requests, history via get_recent_commits. It also supplies the reason behind the first exclusion (the open_issues_and_prs field conflates issues and PRs), which is a real routing rationale rather than a bare name drop.

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