list_topicsLists available interview roles and question-bank topics with question counts by level (Entry/Mid/Senior), so you can identify valid topic IDs before retrieving questions.
List the roles (ai-engineer, investment-banking) and topics in the question bank, with question counts per level (Entry/Mid/Senior). Call this first to get valid topic ids.
| Name | Required | Description | Default |
|---|---|---|---|
| role | No | Limit to one role. Omit for all roles. |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint and closed-world (openWorldHint=false); the description adds that the content is a bounded catalog of two fixed roles with per-level counts, confirming a static lookup rather than a search. It does not describe ordering or pagination, but none is implied for a two-role catalog.
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 short sentences, front-loaded with what is returned, then the action-driving guidance. Nothing redundant.
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?
No output schema exists, but the description covers the returned entities and their aggregation (counts by level), which is enough to call and interpret it. Only the exact response keying is unstated, a minor gap.
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 coverage is 100% and the single enum parameter is fully documented with 'Omit for all roles.' The description restates the enum values but adds no filtering semantics beyond the schema, so baseline 3 applies.
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?
Specific verb (List) plus the exact resources (roles and topics in the question bank) with concrete example values and the return payload (question counts per Entry/Mid/Senior level). The 'call this first' note also distinguishes it from retrieval siblings like get_questions and search_questions.
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?
Explicit sequencing guidance: call this first to obtain valid topic ids, which effectively tells the agent this precedes get_questions/search_questions. It lacks an explicit 'don't use this to fetch questions' exclusion, so a 4 rather than 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.