Lists documentation articles and lets you filter results by category path to quickly locate relevant Formidable Forms docs.
List documentation articles, optionally filtered by category path.
| Name | Required | Description | Default |
|---|---|---|---|
| category | No | Optional category path, e.g. "add-ons/ecommerce". |
| 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 and idempotentHint, so the safety profile is covered. The description adds only that category filtering is optional, and says nothing about whether the full corpus is returned, ordering, or result size limits — behavior an agent might care about for a list operation.
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?
A single front-loaded sentence with no filler or redundancy. It is arguably over-terse given the crowded sibling set, but nothing in it is wasted.
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?
With one optional parameter, full schema coverage, an output schema, and safety annotations, the description covers what the agent minimally needs to invoke it. The remaining gap is routing guidance against the several similar listing/search siblings.
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 schema's own description supplies the format example ('add-ons/ecommerce'). The description only echoes that the category filter is optional, adding no meaning 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.
Does the description clearly state what the tool does and how it differs from similar tools?
The description names a specific verb and resource ('List documentation articles') plus the filtering scope, so the agent knows exactly what the tool returns. It does not distinguish itself from the closely related siblings search_docs and browse_docs_by_category, which is the main clarity gap.
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?
There is no guidance on when to choose this tool over search_docs, browse_docs_by_category, or list_categories, all of which plausibly overlap. 'Optionally filtered by category path' hints at the filter's use, but nothing tells the agent when the unfiltered list is the right call versus a search.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.