Skip to main content
Glama

GStars

Repository snapshot

get_repo
Read-onlyIdempotent

Read one stored repository, its latest measured growth and health. Optional history uses stored star snapshots; it never calls GitHub. Check as_of and last_synced_at before citing counts.

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

Input Schema

NameRequiredDescriptionDefault
nameYesGitHub repository name.
ownerYesGitHub owner or organization.
include_historyNoInclude up to 365 recent stored daily star snapshots.

Output Schema

NameRequiredDescriptionDefault
as_ofYesData-derived observation time or ranking week_start; null if unavailable. Individual repositories can have different freshness.
healthYes
warningsYes
repositoryYes
generated_atYes
schema_versionYes
star_snapshotsYes
weekly_metricsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, closed-world, non-destructive), and the description still adds real value: the data is a stored snapshot that "never calls GitHub," and counts may be stale so the caller should inspect as_of and last_synced_at. That staleness warning is exactly the kind of behavior annotations cannot express.

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?

Three short sentences, front-loaded with what the tool returns, then the history caveat, then the citation warning. Nothing is padded and no sentence restates the tool name or title.

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?

Given rich annotations and an existing output schema, the description only needs to add operational context, and it does so with the staleness caveat. The remaining gap is minor: it doesn't say how the tool behaves when the requested repository is absent from the store or how fresh a snapshot is guaranteed to be.

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 owner, name, and include_history are already documented including the 365-snapshot cap, which sets the baseline at 3. The description reinforces that history is optional and drawn from stored snapshots rather than the API, but adds little beyond the schema's own wording and says nothing about the format of owner/name values.

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 concrete verb and resource ("Read one stored repository") plus what it returns ("latest measured growth and health"), which separates it from plural/list-style siblings like search_repos. It stops short of naming the sibling it is not, so an agent must still infer the boundary from the word "one".

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?

Gives usable guidance for the optional branch (history comes from stored snapshots, not live GitHub) and a citation caveat (check as_of and last_synced_at). However, it never states when to prefer this over search_repos or get_trending, nor what happens when the repository is not in the store, so the when/when-not framing is only implied.

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