Skip to main content
Glama

List topics

list_topics
Read-onlyIdempotent

List companies, people and subjects that have topic pages of sourced facts, most facts first. Filter with query; pass a slug to get_topic.

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 to return, 1-100, default 25
queryNoPart of a topic name, matched as a substring (such as "nvidia" or "AI"); omit to list all
offsetNoHow many to skip, default 0. Pass next_offset from the previous page to get the next page.

Output Schema

NameRequiredDescriptionDefault
totalYes
offsetYes
resultsYes
next_offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, non-destructive and closed-world, so the safety profile is covered. The description adds the ordering trait ("most facts first"), which is genuinely useful and not in annotations, but says nothing about pagination behavior or result size beyond what the schema documents.

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 short sentences with zero filler; the resource definition comes first and the filtering/routing guidance second. 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?

With an output schema present, the description needn't explain return values, and pagination is covered by the offset schema text. It covers what the tool lists, how to filter, and where to go for detail; only the ordering-vs-search distinction among siblings is left implicit.

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 limit, offset and query are already fully documented, establishing a baseline of 3. The description reinforces that query filters by name substring and clarifies that slug is not a parameter of this tool, but adds no syntax or format detail beyond the schema.

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 verb and resource ("List companies, people and subjects that have topic pages of sourced facts") and adds a useful scope qualifier about ordering. It also implicitly distinguishes itself from get_topic by saying a slug goes there instead, though it doesn't differentiate itself from search_facts or search.

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?

"Filter with query; pass a slug to get_topic" gives concrete usage: filter in this tool, then fetch detail in the sibling. It does not state when to prefer this over search_facts or search for fact-level lookups, so it falls short of full when/when-not guidance.

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