Skip to main content
Glama

list_topics

Retrieve read-only topic records—IDs, names, summaries, threads, and pinned conclusions—to check overlaps before merging or choose an existing topic name.

Instructions

List the engineer's topics — id, name, summary, the threads under each, and the conclusion if pinned. Read-only. Use it to see what overlaps before the engineer decides what to merge, or to pick an existing topic name.

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

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does declare 'Read-only' explicitly, plus discloses what is returned including nested threads and the pinned conclusion. It omits any note on result size, ordering, or pagination behavior for a potentially long list.

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?

Two sentences, front-loaded with the payload shape, then the action guidance. Every clause carries information — none of it restates the tool name or is filler.

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?

No output schema exists, so the description correctly compensates by naming the returned fields, which is the key thing an agent needs. What remains thin is scale and ordering information for a list that could contain many topics with nested threads.

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?

The tool takes no parameters, so the baseline of 4 applies; there is nothing for the description to disambiguate. The description does not waste words inventing parameter semantics that do not exist.

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?

States a specific verb and resource ('List the engineer's topics') and enumerates the returned fields (id, name, summary, threads under each, pinned conclusion), which separates it from list_threads and list_cases. The scope qualifier 'the engineer's topics' also sets it apart from global search tools like search_prior.

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?

Gives two concrete when-to-use scenarios: inspecting overlap before a merge decision, and picking an existing topic name. That implicitly steers away from merge_topic/define for the read path, though it never states a 'do not use for X' exclusion.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.