Skip to main content
Glama

Get a project's write-up

get_repo

Full Repolode write-up of one GitHub project: summary, description, features, use cases, quick start commands, limitations, license, stars, what it replaces, and maintenance signals (recent commits and contributors, releases, CI, tests, issue responses).

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

Input Schema

NameRequiredDescriptionDefault
repoYesGitHub repo as 'owner/name' or its URL.
localeNoLanguage of the summaries; default en.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does disclose the returned content set in detail, and 'get' implies a read, but it omits whether the write-up is generated on demand (latency/cost), what happens for private, missing, or unknown repos, and any auth or rate-limit behavior.

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?

A single dense sentence that front-loads the core claim ('Full Repolode write-up of one GitHub project') before the field inventory. The long enumeration is justified because it defines the tool's scope, though it could be tightened into a shorter list.

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?

There is no output schema, so the description must describe the return payload, and it does so comprehensively. What remains missing is error behavior for unknown repos and whether the content is freshly generated or cached, which matters for a two-parameter fetch 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 both the repo identifier format and the locale enum are already documented. The description adds no extra meaning about the repo parameter and only indirectly implies that locale drives the language of the write-up, so the baseline of 3 applies.

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 resource (the full write-up of one GitHub project) and enumerates exactly what that write-up contains, so it is clearly distinct from a search or listing tool. It doesn't explicitly name or contrast with siblings like search_repos or trending, leaving that inference to the agent.

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?

Usage is only implied: the description makes clear it retrieves a single project's detail page, which suggests it is the drill-down after a search, but it never says when to prefer it over find_alternatives/get_collection or what to do if the repo is unknown. No exclusions or prerequisites are stated.

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