Skip to main content
Glama

Best of Go

Trending Go repos

trending_repos
Read-onlyIdempotent

The 10 Go repos that gained the most stars yesterday, in the last 7 days, or in the last 30 days, or the 10 with the most stars of all time.

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

Input Schema

NameRequiredDescriptionDefault
rangeNoOne of yesterday, 7d, 30d, or all. Default 7d. all ranks by total stars.

Output Schema

NameRequiredDescriptionDefault
rangeYes
reposYes
sinceNo

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 declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds real context beyond that: results are capped at 10 with no pagination implied, the language is fixed to Go, and 'all' switches the ranking basis from star gain to total stars. Return shape is left to the output schema, which exists.

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?

One sentence, front-loaded with the resource and ranking metric, with no filler. The chained 'or ... or ...' construction is slightly clunky and repeats the range values the schema already lists, costing a point.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a simple, zero-required-parameter read tool with full schema coverage, annotations, and an output schema. The description covers scope, ranking basis, and result count — everything an agent needs before invoking it correctly.

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% and the single 'range' parameter already documents its four values, the 7d default, and what 'all' means. The description restates the same enumerations without adding format or edge-case detail, so it neither compensates for nor improves on the schema. Baseline 3 applies.

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 names a precise resource (Go repos), a precise ranking metric (stars gained) and a fixed result count (10), plus the alternative 'all time' mode. It is unmistakably different from siblings like search_repos or get_repo. It stops short of 5 only because it is a noun phrase with no verb and never names an alternative tool.

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?

The time-window options imply when the tool is appropriate (browsing trending Go projects over a period), but there is no explicit when-to-use or when-not-to-use guidance. Nothing tells the agent to prefer search_repos for a targeted query or star_history for a specific repo's trajectory.

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