Skip to main content
Glama

Best of Go

Go repos by topic

topic_repos
Read-onlyIdempotent

The Go repos with one GitHub topic, a tag repo authors set, ranked by stars gained in the last 30 days and by total stars, with related topics. For curated groups, use category_repos.

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": {
      "topic": "<topic>"
    },
    "name": "topic_repos"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many repos to return in each list, 1 to 50. Default 10.
topicYesA GitHub topic, such as cli, orm, or web-framework. Use list_topics to find one.

Output Schema

NameRequiredDescriptionDefault
urlYes
topicYes
most_starsYes
repo_countYes
total_starsYes
trending_30dYes
related_topicsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and idempotentHint, so safety and repeatability are covered. The description adds useful behavior: results are ranked two ways (30-day star gain and total stars) and include related topics, plus a constraint of exactly one topic. It does not disclose ordering of the returned lists, tie-breaking, or pagination beyond the limit parameter.

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?

A single front-loaded sentence carries the resource, scope, ranking criteria, and return content, and the second short sentence routes to the alternative. No redundant restatement of the name or schema.

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?

With an output schema present, the description need not explain return values, and annotations cover the safety profile; the ranking criteria it does mention are genuinely additive. Minor gap: it does not state how many lists come back or how related topics are derived, which slightly limits predictability for a two-list ranked response.

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 coverage is 100%, so the baseline is 3, and the description goes beyond it by explaining that the topic must be a single tag rather than a group, and by characterizing what the lists represent (ranked by recent star gain and total stars). It says nothing extra about limit beyond the schema's 1-50 default of 10.

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?

The description states a specific verb-like operation and resource: Go repos carrying a single GitHub topic, ranked by 30-day star gain and total stars, plus related topics. It explicitly distinguishes itself from category_repos for curated groups, so an agent can separate it from that sibling without opening either schema.

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?

It clearly signals the when-to-use case (a single GitHub topic tag) and names the alternative (category_repos) for curated groups. It also implies list_topics as a discovery path via the schema, but gives no explicit exclusions such as when to prefer search_repos or trending_repos.

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