Skip to main content
Glama

Best of Go

List topics

list_topics
Read-onlyIdempotent

GitHub topics, tags repo authors set, that at least 10 tracked Go repos carry, most repos first. Categories (list_categories) are the curated groups; topics narrow them down.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many topics to return, 1 to 500. Default 50.
containsNoOnly topics whose name contains this text, such as sql.

Output Schema

NameRequiredDescriptionDefault
topicsYes
matchingYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so safety is covered. The description does add meaningful behavior beyond that: the >=10 tracked Go repos inclusion threshold and the most-repos-first ordering, both of which shape what comes back. It says nothing about how results are paged or what the response contains, so with an output schema present it lands mid-range rather than high.

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 sentences, no filler, with the scoping threshold and ordering front-loaded. The first sentence is a dense fragment with stacked clauses ('tags repo authors set, that at least 10 tracked Go repos carry, most repos first') that takes a second read, but every clause carries information.

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?

For a two-parameter read-only list tool with an output schema and full annotation coverage, the description supplies the essential domain context: what a topic is, the population threshold, the sort order, and the relationship to categories. The remaining gap is the meaning of 'tracked Go repos' (the dataset's scope), which an agent may need to interpret the threshold 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 description coverage is 100%, with limit (1-500, default 50) and contains fully documented in the schema. The description only gestures at filtering via 'topics narrow them down' and adds no syntax or format detail for contains. Baseline 3 is appropriate when the schema carries all parameter meaning.

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 defines the resource precisely: GitHub topics ("tags repo authors set") that are carried by at least 10 tracked Go repos, ordered most-repos-first. It explicitly distinguishes itself from list_categories by framing topics as narrower than curated categories. It loses a point only because it is written as a fragment with no explicit verb, so the action has to be inferred from the name/title.

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 gives a clear relational rule for choosing between this tool and list_categories: categories are the curated groups, topics narrow them down. What's missing is an explicit 'use this when' condition, such as when the agent wants fine-grained tags rather than curated groupings, and there is no statement about when not to use it.

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