Skip to main content
Glama

get_repo

Read-only

Read HotRepo's full review of a repository (Markdown), with its stats, topic, daily trending history (the all-languages board; each day's best_github_rank_that_day is the best position it reached on GitHub's page that day, null before 2026-10-24) and Hacker News threads that link to it. forked_from / fork_root name the upstream repository when it is a GitHub fork (null otherwise). Only repositories that have trended and been reviewed are available.

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": {
      "full_name": "<full_name>"
    },
    "name": "get_repo"
  }
}

Input Schema

NameRequiredDescriptionDefault
full_nameYesGitHub repository as owner/repo (a github.com URL also works)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / lang
      Removed value: -{
      -  "default": "en",
      -  "description": "Language of reviews and topic names",
      -  "enum": [
      -    "en",
      -    "zh"
      -  ],
      -  "title": "Lang",
      -  "type": "string"
      -}
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description goes further by specifying the return format (Markdown) and explaining field semantics, including that best_github_rank_that_day is a daily best position that is null before 2026-10-24 and that forked_from/fork_root are null for non-forks. It doesn't discuss error behavior or payload size for repos with long histories, but the added value over annotations is substantial.

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?

The core purpose is front-loaded in the first clause, and the follow-on clauses each carry distinct information about contents and edge cases. The long nested parenthetical about ranking semantics is somewhat dense and could be split, but no sentence is filler.

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 single-parameter, read-only lookup with an output schema already present, the description covers everything an agent needs: what is returned, the format, the availability restriction, and the null-case rules for rank and fork fields. Nothing material is left to inference before calling it.

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 already documents the owner/repo format and that a github.com URL is accepted. The description adds no additional parameter meaning, so the baseline of 3 applies even though nothing is missing.

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 opens with a specific verb and resource ('Read HotRepo's full review of a repository') and enumerates the payload (stats, topic, daily trending history, Hacker News threads), which lets an agent distinguish it from narrower siblings like get_star_history or get_trending. It never names those siblings or explicitly contrasts scopes, so it falls 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 Guidelines3/5

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

It gives a real eligibility precondition ('Only repositories that have trended and been reviewed are available'), which is useful when-to-call guidance. However, there is no statement of when to prefer this over compare_repos, get_similar_repos, or get_trending, and no note on what to do when a repo is ineligible.

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