Skip to main content
Glama

compare_repos

Read-only

[Pro] Compare 2 to 5 repositories side by side: stars, forks, age, language, license, HotRepo topic and one-line review, days on GitHub's all-languages daily Trending (HotRepo's records start 2026-05-10) and best position there (real positions from 2026-10-24), recent star growth (when HotRepo has generated its star history; null otherwise) and Hacker News attention. stars_gained_last_7_days and stars_gained_last_30_days count back from star_growth_until, which can differ between repositories; mention it when the dates differ instead of comparing the numbers as if they covered the same days. For the full reviews call get_repo on the ones that matter. Repositories without a HotRepo page (no review and no star history) are returned with available=false.

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_names": "<full_names>"
    },
    "name": "compare_repos"
  }
}

Input Schema

NameRequiredDescriptionDefault
full_namesYes2 to 5 GitHub repositories as owner/repo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only say readOnlyHint=true and openWorldHint=false; the description adds substantial behavior beyond that: the [Pro] tier requirement, data provenance windows (trending records from 2026-05-10, positions from 2026-10-24), null semantics for star history and Hacker News attention, and the available=false shape for repos without a HotRepo page. The star_growth_until caveat is genuinely operationally important — it warns that the 7/30-day windows can cover different date ranges across repos so the numbers must not be read as apples-to-apples.

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?

Front-loaded with the verb and resource, and nearly every clause conveys a distinct operational fact. It is dense to the point of being one long run-on sentence, and the critical star_growth_until warning is buried mid-paragraph rather than surfaced, which slightly hurts scannability.

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?

An output schema exists, so return values need no explanation, yet the description usefully covers the edge cases an agent must handle: tier gating, null star history, differing growth windows, and missing HotRepo pages. For a one-parameter comparison tool this leaves no material gap an agent would need 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?

There is a single parameter and schema coverage is 100%, with the schema already documenting '2 to 5 GitHub repositories as owner/repo' plus minItems/maxItems. The description restates the 2-to-5 bound but adds no new meaning about the full_names format or validation. Baseline 3 is appropriate when the schema carries the parameter semantics.

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 bounded scope ('Compare 2 to 5 repositories side by side') and enumerates exactly which attributes are compared (stars, forks, age, language, license, topic, review, trending days/position, star growth, HN attention). This is clearly distinct from sibling get_repo, which the description itself names as the source of full reviews.

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?

Gives explicit routing: 'For the full reviews call get_repo on the ones that matter,' establishing compare_repos as the shallow side-by-side view and get_repo as the deep dive. It also states the fallback behavior for repos without a HotRepo page (available=false). It stops short of an explicit 'use this instead of get_similar_repos when...' condition, so it is clear context without full exclusions.

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