Skip to main content
Glama

get_star_history

Read-only

[Pro] A repository's star growth over its whole life: stars at the end of each month, stars added on each of the last 30 days, stars gained over the last 7 / 30 / 90 / 365 days, and the days it was on GitHub's all-languages daily Trending page with its best position that day (HotRepo's board records start 2026-05-10; real positions from 2026-10-24, earlier ones are null). Counts are from GitHub's star history and only include stars that still exist. If HotRepo has not fetched this repository yet, the call fetches it from GitHub now (usually a few seconds), which uses one of the plan's new star histories for the day; repositories already on HotRepo do not count.

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

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. Added

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the readOnly/openWorld annotations, the description discloses a real side effect: an unfetched repository is pulled from GitHub during the call, taking a few seconds and consuming one of the plan's new star histories for the day, while already-tracked repos do not count. It also states data provenance (GitHub star history, only surviving stars) and null semantics for pre-2026-10-24 Trending positions.

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 value proposition is front-loaded in the first clause, then caveats follow in a logical order (provenance, then fetch/quota behavior). It is dense and long for one sentence-per-idea, and the Trending board date caveat is verbose, 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?

Given an output schema exists, the description need not explain return values, and it covers everything else an agent needs: what the data means, quota cost, latency, provenance limits, and null behavior. Nothing required to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is a single required parameter whose schema already documents it at 100% coverage, including that a github.com URL is accepted. The description adds no parameter-specific meaning, but with one fully documented parameter the baseline of 4 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?

The description names a specific resource (a repository's star growth) and enumerates exactly what is returned: month-end totals, last-30-day daily additions, 7/30/90/365-day gains, and Trending-page appearances with best position. That is far more precise than a name restatement, but it never explicitly contrasts itself with adjacent siblings such as get_repo or get_trending, so it stops 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?

Usage is only implied: an agent can infer you call this when you need historical star growth rather than general repo metadata. There is no explicit when-to-use/when-not statement and no named alternative for cases like comparing two repos' growth (compare_repos) or general repo lookup (get_repo).

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