list_articlesPaginated list of articles from Therapy for Teens. Returns title, slug, summary, and URL.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number (1-indexed). | |
| limit | No | Max results per page (default 30, max 100). |
Changes observed during successful MCP inspections.
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"Input schema / $schemaAdded value: +"http://json-schema.org/draft-07/schema#"Input schema / properties / limit / descriptionPrevious value: -"Page size (default 30, max 100)."New value: +"Max results per page (default 30, max 100)."Input schema / properties / limit / maximumAdded value: +100Input schema / properties / limit / minimumAdded value: +1Input schema / properties / limit / typePrevious value: -"number"New value: +"integer"Input schema / properties / page / descriptionPrevious value: -"Page number (default 1)."New value: +"Page number (1-indexed)."Input schema / properties / page / maximumAdded value: +9007199254740991Input schema / properties / page / minimumAdded value: +1Input schema / properties / page / typePrevious value: -"number"New value: +"integer"Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, so the tool is known to be safe. The description adds transparency about pagination behavior and return fields (title, slug, summary, URL), which are useful context beyond the annotation.
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?
The description is one concise sentence, front-loaded with the purpose, and contains no redundant information. Every word adds value.
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?
For a simple list tool with full schema coverage and a read-only annotation, the description is sufficiently complete. It mentions pagination and return fields, though it omits details like ordering or total count, which are not critical for this tool.
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 description coverage is 100%, so parameters are fully documented in the input schema. The description adds no additional meaning about page or limit, so a baseline score of 3 is appropriate.
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 clearly states a specific verb (list) and resource (articles), scopes it to 'Therapy for Teens', and mentions return fields. This distinguishes it from siblings like get_article and search_articles.
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?
The description provides no explicit guidance on when to use this tool versus alternatives. It does not mention that search_articles should be used for filtering or that get_article is for single articles, leaving usage decisions to the agent.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.