Skip to main content
Glama

Browse or search open discussion

list_topics
Read-only

Discussion topics: newest first, by latest reply (sort "active"), or best match with query. The tag "site-feedback" holds suggestions for this site. get_topic reads one.

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
tagNoOnly topics with this tag, for example "site-feedback".
sortNo"new" (default): newest topic first. "active": latest reply first.
limitNoHow many topics to return.
queryNoWords to look for in titles and bodies, 2 to 100 characters.
beforeNoNext page of "new": next_before from the previous result.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / before / description
      Previous value: -"For the next page of \"new\": the next_before value from the previous result."New value: +"Next page of \"new\": next_before from the previous result."
  2. 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 openWorldHint=true, so the safety profile is covered. The description adds the default ordering (newest first) and the meaning of the site-feedback tag, which is genuine domain context, but says nothing about page size behavior, whether all fields of a topic are returned, or what an empty query result looks like.

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?

Three short sentences, front-loaded with the resource and its ordering modes before the cross-reference. It is efficiently sized; the telegraphic phrasing ('Discussion topics: newest first...') trades a little readability for density but wastes no words.

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

Completeness3/5

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

For a zero-required-parameter list tool with full schema coverage and readOnly annotations, the essentials are covered. However, there is no output schema, and the description never sketches what a result item contains or how 'before' paging interacts with the sort modes, leaving those to inference.

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%, so every parameter is already documented, and the description largely restates it ('best match with query', sort "active" = latest reply). The one thing it adds beyond the schema is the tag example's semantic purpose, which is marginal. Baseline 3 applies when the schema carries the parameter burden.

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?

Names the resource (discussion topics) and the three retrieval modes (newest first, latest-reply order, match-by-query), and explicitly separates itself from the read-one sibling: 'get_topic reads one.' The verb is only implicit in the noun-phrase framing, but the combination of title and description leaves no ambiguity about what is returned.

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?

Guidance is present through the sort/query mapping and the explicit pointer that reading a single topic is get_topic's job. It also gives a concrete domain route: use tag "site-feedback" for site suggestions. It stops short of saying when to prefer this over sibling list/search tools, so it is clear context rather than full when/when-not coverage.

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