Skip to main content
Glama

GStars

Trending repositories

get_trending
Read-onlyIdempotent

Ranked recent star growth in the latest measured ranking week. window=30d returns 30-day growth and rank. Returned ranks are site-wide, even when filtering by category/topic.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_trending"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results, up to 100.
offsetNoZero-based offset; use next_offset/next from the response. Narrow the query if truncated=true.
windowNoGrowth window.7d
categoryNoCurated category or GitHub topic slug; canonical URL aliases are accepted.

Output Schema

NameRequiredDescriptionDefault
nextYes
as_ofYesData-derived observation time or ranking week_start; null if unavailable. Individual repositories can have different freshness.
countYes
itemsYes
windowYes
categoryYes
has_moreYes
truncatedYes
week_startYes
next_offsetYes
generated_atYes
schema_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, non-open-world behavior. Beyond that, the description adds non-obvious ranking semantics: rankings are tied to the latest measured week, 30d affects growth/rank meaning, and ranks stay site-wide even under category/topic filters. It does not cover pagination or truncation, but the schema does.

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 the ranking basis and followed by the two most important caveats. No filler or redundant restatement of schema fields.

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?

The tool has four optional parameters and an output schema, so the description does not need to explain pagination or return fields. It covers the ranking model and one key subtlety but leaves alternative-tool routing implicit.

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?

Schema descriptions are fully covered, giving a baseline of 3. The description adds meaning beyond the schema by clarifying what window=30d changes and that category/topic filtering does not localize the returned rank.

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 gives a specific resource and ranking basis: recent star growth in the latest measured ranking week. It is distinguishable from repository lookup, category listing, and search tools by being a ranked trending list, though it does not explicitly name those alternatives.

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 establishes the context of consulting a weekly star-growth ranking and gives an important filtering caveat for category/topic. However, it never states when to choose this over search_repos or get_repo, nor any when-not conditions, so guidance is implied rather than explicit.

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