Skip to main content
Glama

GStars

Search and rank repositories

search_repos
Read-onlyIdempotent

Find tracked repositories by text, category/topic and language. Most popular means total stars. Stable server-side sorting happens before pagination.

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": "search_repos"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoSearch repository name/description and exact topic.
sortNoPopularity or last code update.stars
limitNoMaximum results, up to 100.
offsetNoZero-based offset; use next_offset/next from the response. Narrow the query if truncated=true.
categoryNoCurated category or GitHub topic slug; canonical URL aliases are accepted.
languageNoExact GitHub language, for example Python or TypeScript.

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description does add two real behavioral facts beyond that: what 'most popular' means (total stars) and that sorting is server-side and stable before pagination, which matters for offset paging. It stops short of describing result ranking beyond the sort key.

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?

Three short sentences, front-loaded with the purpose, with no filler. The pagination-ordering sentence is dense but earns its place by clarifying an ambiguity an agent would otherwise hit when combining sort with offset.

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?

An output schema exists and the input schema is fully described, so return values and parameter formats need no coverage. Purpose, sort semantics and pagination ordering are all addressed. The only soft gap is the unexplained 'tracked' scoping (what corpus, any auth requirement), which is modest for an annotated read-only tool.

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%, so the schema already documents q, sort, limit, offset, category and language, including the offset/next_offset guidance and truncated handling. The description's 'most popular means total stars' sharpens the sort enum's meaning slightly, which is a marginal add over 'Popularity or last code update' in the schema.

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 specific verb ('Find') and a well-scoped resource ('tracked repositories') plus the three facets searchable (text, category/topic, language). This reads clearly as a multi-facet search rather than a single-record fetch like get_repo, though it never names a sibling or explicitly contrasts scope.

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 'use this to look up repos' from the verb and facets. There is no explicit when-to-use vs. when-not guidance, no mention of when to prefer get_repo or get_trending, and no stated prerequisites for the 'tracked' qualifier.

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