Skip to main content
Glama

cd_topics

cd_topics
Read-only

Browse pages of Chief Delphi topic listings to survey what is being discussed by newest, newly created, or most-engaged order, optionally scoped to one category.

Instructions

Browse a page of Chief Delphi topic listings: newest (mode=latest), newly created (mode=new), or most-engaged (mode=top with a period). Optionally scope to one category. Use this to survey what is being discussed rather than to look for a specific phrase (use cd_find for that). Each row carries the topic id, slug, category id, post count, view count and last activity; feed ids to cd_raw or cd_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": "cd_topics"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoListing feed to read. Default "latest".
pageNoZero-based page; each page is ~30 topics. Default 0.
limitNoRows to print from the page. Default 30.
orderNoSort order for the listing. Defaults to the feed order.
periodNoFor mode=top only. Default "monthly".
categoryNoCategory id, slug or exact name (see cd_categories). Omit for the whole forum.
max_charsNoCap the reply at this many characters (default 20000).

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?

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and external-data profile are covered. The description adds value beyond that by naming the exact fields each row carries, which matters because there is no output schema, and by stating the category scoping option. It does not mention rate limits or what happens when max_chars truncates the reply.

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?

Three sentences, front-loaded with the resource and its modes, then the disambiguation, then the payload shape. Every sentence carries distinct information with no 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?

With no output schema, the row-field enumeration is exactly the missing piece, and the sibling routing covers the workflow context. Minor gap: it does not explain how page/limit interact or what a max_chars-truncated response looks like, though those are largely covered in the schema.

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 every parameter including the mode/order/period enums is already documented in structured form. The description restates the mode values and category scoping without adding syntax or format detail beyond the schema, so the baseline 3 applies.

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 ('Browse a page of Chief Delphi topic listings') and immediately enumerates the three modes with their parameter values, so the agent knows exactly what the tool returns. It explicitly separates itself from cd_find ('look for a specific phrase'), which is the nearest sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit use case ('survey what is being discussed') plus the exclusion condition that routes to the alternative ('use cd_find for that'), and adds a downstream chaining hint ('feed ids to cd_raw or cd_topic'). Nothing about when to pick this tool over its siblings is left to inference.

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