list_topicsList public topic names, slugs and record counts. Use a slug as the topic filter in search or list_days.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| offset | No |
| Name | Required | Description | Default |
|---|---|---|---|
| limit | Yes | ||
| total | Yes | ||
| offset | Yes | ||
| results | Yes | ||
| provenance | Yes | ||
| next_offset | Yes |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is well covered. The description adds the 'public' scope, which is useful, but does not disclose pagination behavior or any other runtime characteristics beyond what the schema's limit/offset parameters imply.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences with no filler. The core purpose is stated first, and the usage hint is secondary but still valuable. Every sentence earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple paginated list tool with read-only annotations and an output schema, the description conveys the essential purpose and how results connect to sibling tools. It could mention pagination explicitly, but the limit/offset parameters and output schema cover most of what an agent needs.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description needed to compensate for the limit and offset parameters. It does not mention them at all; it only describes the output. The parameter names and constraints are somewhat self-explanatory, but the description provides no additional meaning such as pagination semantics or result ordering.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb ('List'), a clear resource ('public topics'), and the exact data returned ('names, slugs and record counts'). This distinguishes it from the sibling tools, which are about retrieval or listing days, not topic enumeration.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives concrete guidance on how the output should be used ('Use a slug as the topic filter in search or list_days'), which tells the agent the purpose of the returned slugs. It does not explicitly exclude cases where this tool should not be used, but the context is clear enough for selection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a distinct purpose: fetching a specific day, listing days by date, listing topics, and searching by text/topic. There is no meaningful overlap between them, and the descriptions clarify the boundaries well.
The names are clear and lowercase, with list_days and list_topics following a consistent verb_noun pattern. fetch and search are bare verbs rather than fetch_day or search_days, creating a minor but understandable deviation.
Four tools is well-suited to this server's focused purpose: searching, browsing by date, browsing topics, and fetching detailed records. Each tool earns its place without redundancy or unnecessary surface area.
For a read-only reference domain, the tool set covers the full workflow: discover via search or topic, list by date range, and retrieve full details. No obvious missing operation or dead end is apparent.