Retrieve list.am category IDs and names; pass a parent category ID to get its subcategories for ad filtering and browsing.
List list.am categories (ID and name). Pass a category_id to see its subcategories.
| Name | Required | Description | Default |
|---|---|---|---|
| category_id | No | Parent category ID. Omit for the top-level categories. |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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=true and openWorldHint=true, covering the safety and network profile. The description adds the hierarchical listing behavior but says nothing about pagination, limits, or return ordering. Adequate but not rich.
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, the core listing behavior front-loaded and the parameter effect second. Zero wasted words.
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?
An output schema exists so return values need no explanation, and the tool has a single optional parameter. The description covers what is listed and how the parameter alters scope; only minor operational details (ordering, item limits) are absent.
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%, so the baseline is 3, but the description goes beyond the schema field text by explaining that a category_id switches the call from top-level categories to that category's subcategories, clarifying the semantic effect of the parameter.
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 names a specific verb (List) and resource (list.am categories) and even states what is returned (ID and name). No sibling tool handles categories, so an agent can select this without opening the schema.
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?
It gives a clear conditional: pass a category_id to get subcategories, omit it implicitly for top-level. There is no explicit when-not or named alternative, but the sibling set contains no competing category tool, so the guidance is sufficient for correct invocation.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.