Skip to main content
Glama

cd_categories

cd_categories
Read-only

List Chief Delphi forum categories and subcategories with numeric IDs and slugs so you can scope searches and browses to a specific area. Use the returned IDs in topic and find calls.

Instructions

List every Chief Delphi (chiefdelphi.com) category and subcategory with its numeric id and slug. Call this first when you need to scope a search or browse to a forum area such as Technical, Competition or Announcements. Read-only, no login. Returns ids usable in cd_topics/cd_find category=.

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_categories"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the description does not need to re-argue safety, yet it usefully adds 'no login' (no auth prerequisite) and tells the agent what the payload contains: ids and slugs usable elsewhere. No rate limits or ordering/pagination behavior is mentioned, which is the remaining gap.

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 short sentences, front-loaded with what is returned, then when to call it, then the safety/auth note and downstream usage. Every sentence carries information an agent needs; nothing is redundant with the title.

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

Completeness5/5

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

No output schema exists, but the description compensates by naming the returned fields (numeric id and slug) and the exact parameter they feed (`category=` on cd_topics/cd_find). For a zero-parameter enumeration tool with annotation coverage, nothing needed to invoke or chain it is missing.

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 zero parameters, so there is nothing for the description to disambiguate; the baseline for an empty schema applies. The description correctly avoids inventing arguments and instead explains how the returned values are consumed as inputs elsewhere.

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 every Chief Delphi category and subcategory') plus what each entry carries ('numeric id and slug'). That is clearly distinct from the sibling tools, which are topic/find/raw/user oriented, so no ambiguity about which tool enumerates categories.

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 explicit ordering guidance ('Call this first when you need to scope a search or browse to a forum area') with concrete example areas. It names the downstream consumers cd_topics/cd_find with the `category=` argument, so an agent knows the follow-up call; it stops short of stating when NOT to use it, which keeps it from a top score.

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