Skip to main content
Glama

Best of Go

Go repos in a category

category_repos
Read-onlyIdempotent

The repos of one category, ranked by total stars or by stars gained in the last 30 days, with archived repos last. Repos awesome-go lists come first; classified marks repos a classifier added.

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": {
      "category": "<category>"
    },
    "name": "category_repos"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNostars (default) ranks by total stars; trending ranks by stars gained in the last 30 days.
limitNoHow many repos to return, 1 to 50. Default 20.
categoryYesA category slug from list_categories, such as web-frameworks or orm.

Output Schema

NameRequiredDescriptionDefault
sortYes
reposYes
sourceYes
categoryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedOutput schema / properties / category / properties / classified_repos
      Added value: +{
      +  "type": "integer"
      +}
    • addedOutput schema / properties / category / properties / group
      Added value: +{
      +  "type": "string"
      +}
    • changedOutput schema / properties / category / required
      Previous value: -[
      -  "slug",
      -  "name",
      -  "description",
      -  "repos",
      -  "stars",
      -  "stars_gained_30d",
      -  "url"
      -]New value: +[
      +  "group",
      +  "slug",
      +  "name",
      +  "description",
      +  "repos",
      +  "classified_repos",
      +  "stars",
      +  "stars_gained_30d",
      +  "url"
      +]
    • addedOutput schema / properties / repos / items / properties / classified
      Added value: +{
      +  "type": "boolean"
      +}
    • changedOutput schema / properties / repos / items / required
      Previous value: -[
      -  "full_name",
      -  "owner",
      -  "name",
      -  "description",
      -  "topics",
      -  "stars",
      -  "url",
      -  "github_url",
      -  "archived"
      -]New value: +[
      +  "full_name",
      +  "owner",
      +  "name",
      +  "description",
      +  "topics",
      +  "stars",
      +  "url",
      +  "github_url",
      +  "archived",
      +  "classified"
      +]
  2. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, idempotentHint), yet the description adds real ordering behavior beyond them: archived repos sort last, awesome-go-listed repos come first, and classifier-added repos carry a 'classified' mark. It stops short of stating anything about limits, pagination, or whether the provenance ordering is stable.

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?

Two compact sentences with the resource and ranking front-loaded. The provenance sentence ('Repos awesome-go lists come first; classified marks repos a classifier added') is terse to the point of being slightly cryptic, but it earns its place by explaining output ordering.

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?

A simple read-only list tool with a full output schema and complete parameter documentation; the description's job is mostly ordering semantics, which it covers. Nothing critical is missing, though a one-line pointer to search_repos/topic_repos for other scopes would round it out.

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 both sort and limit are already documented, and the description's 'ranked by total stars or by stars gained in the last 30 days' largely restates the sort enum meanings. Baseline 3 applies; the description adds no syntax or constraint detail the schema lacks.

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 resource and scope: 'the repos of one category', plus the ranking rules. An agent can tell this apart from owner_repos/topic_repos by scope, but the description never names or contrasts a sibling explicitly, so differentiation is implicit rather than stated.

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 implied by the required category slug ('a category slug from list_categories' in the schema), which routes the agent to the right discovery tool. There is no explicit when-to-use vs search_repos/topic_repos/trending_repos guidance and no exclusions, so the agent must infer the boundary.

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