Teen-first library on CBT, DBT, and finding the right therapist.
Scored across 6 tools
Each tool serves a distinct purpose: fetching a single article, listing articles, searching, citing, retrieving crisis resources, and getting site info. There is no overlap or ambiguity between them.
All tool names follow a consistent verb_noun snake_case pattern (cite_article, get_article, list_articles, search_articles, etc.). The verbs accurately describe the action and the nouns are clear.
Six tools is appropriate for a read-only content library. Each tool covers a necessary functionality (list, search, get, cite, plus safety and context) without unnecessary bloat or missing essentials.
The tool surface fully covers the core domain of accessing articles: listing, searching, retrieving, and citing. The addition of crisis resources and microsite info completes the lifecycle for a safe, well-rounded library. No obvious gaps.
Get a formatted citation for a Therapy for Teens article. Supports AMA, APA, and Chicago styles.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Article slug. | |
| format | No | Citation style (default ama). |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotation readOnlyHint=true already establishes this as a safe read operation, lowering the burden on the description. The description adds the context that it supports multiple citation styles, which is useful but not a deep behavioral disclosure. No mention of potential errors, output format details, or limitations, so it is 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?
The description is two sentences long, front-loaded with the core purpose, and contains no filler. Every word earns its place: it states the action, the resource, and the style options succinctly.
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 retrieval-like tool with full schema coverage and a read-only annotation, the description is sufficient. No output schema exists, but the concept of a 'formatted citation' is self-explanatory. It doesn't cover every edge case (e.g., invalid slug handling), but overall the tool is well-specified.
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%, with both slug and format explained directly in the input schema. The description repeats the style names (AMA, APA, Chicago) that are already enumerated in the format property, adding no new semantic value. Therefore, the baseline of 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 uses a specific verb and resource: 'Get a formatted citation for a Therapy for Teens article.' This clearly distinguishes it from sibling tools like get_article, list_articles, and search_articles, which retrieve or list content rather than produce citations. The supported styles (AMA, APA, Chicago) further clarify the tool's niche.
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 implies the tool is for generating citations, which is clear context for when to use it. It does not explicitly name alternatives or exclusions, but the sibling tools are obviously different in purpose (search/list/retrieve content). The absence of explicit when-not guidance is a minor gap, hence 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.
Fetch a single article from Therapy for Teens by slug. Returns title, body content, author, clinical reviewer, citations, and metadata.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Article slug. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With readOnlyHint=true already provided, the description adds value by specifying the returned fields (title, body, author, clinical reviewer, citations, metadata). This gives the agent a clear expectation of the output without over-explaining.
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 two concise sentences, front-loaded with the primary purpose, followed by the return format. Every word is useful and there is no redundancy.
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 read-only fetch tool with one parameter and no output schema, the description fully covers what the tool returns and how to call it. No critical information is missing.
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?
The schema already covers the 'slug' parameter with a description. The description mentions 'by slug' but adds no additional meaning beyond what the schema provides, so the baseline of 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 clearly states the action ('Fetch a single article'), the resource ('a single article from Therapy for Teens'), and the method ('by slug'). It naturally distinguishes itself from sibling tools like list_articles and search_articles by emphasizing the singular, slug-based retrieval.
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 implies the appropriate scenario: when you have a specific slug and need one complete article. It does not explicitly mention alternatives or exclusions, but the contrast with list/search tools is evident from the phrasing.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Return the canonical 988 / 911 / Crisis Text Line payload. Surface this immediately whenever the user signals self-harm or imminent danger.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already provide readOnlyHint: true. The description adds that the payload is 'canonical' and suggests it should be surfaced with urgency, which is useful behavioral context beyond the annotation. No contradictions with the read-only 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?
Two sentences, no redundant words. The first sentence states the function and the second gives usage guidance. Perfectly sized and front-loaded.
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 tool with no parameters, no output schema, and a straightforward read-only action, the description fully covers its purpose, usage trigger, and distinguishes it from all siblings. It is complete.
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?
The tool has zero parameters, so the baseline is 4. The description mentions no parameters, but none exist to document, so no additional value is needed.
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 ('Return') and resource ('canonical 988 / 911 / Crisis Text Line payload'). It distinguishes itself from siblings that handle articles/microsite info, making the purpose unambiguous.
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?
Explicitly states when to use: 'immediately whenever the user signals self-harm or imminent danger.' This is a clear trigger condition. Since no alternative tool exists for this purpose (siblings are about articles), no exclusions are necessary.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Identity and links for Therapy for Teens: tagline, audience, focus, publisher, sponsor relationship to Emora Health, and key URLs.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The readOnlyHint annotation already declares this is a safe read operation. The description adds no additional behavioral context, but for a simple info retrieval tool, this is acceptable and does not contradict 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 a single, well-structured sentence that front-loads the purpose and lists specific content areas without any extraneous information.
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?
The description provides a thorough list of content areas and is sufficient for a tool with no parameters and no output schema. It clearly conveys what the agent can expect to receive, though it stops short of describing the exact return format.
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?
There are zero parameters, so the description has no parameter documentation burden. The baseline of 4 applies because the schema is empty and no explanation is needed.
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 the tool returns identity and links for the Therapy for Teens microsite, listing specific content categories (tagline, audience, focus, publisher, sponsor relationship, URLs). This distinguishes it from sibling tools that handle articles and crisis resources.
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?
No guidance is provided on when to use this tool versus the sibling tools. The description only lists what it returns, with no mention of alternatives or exclusions, leaving the agent to infer its purpose.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Paginated 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). |
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.
Search Therapy for Teens's editorial corpus by query. Returns title, slug, summary, and URL for matching articles.
| Name | Required | Description | Default |
|---|---|---|---|
| q | No | Alternate parameter name for `query`. | |
| limit | No | Max results (default 10, max 50). | |
| query | Yes | Free-text search query. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The readOnlyHint annotation already covers the safety profile. The description adds the scope ('editorial corpus') and return fields, but does not disclose further behavioral traits like pagination behavior or ordering. It provides some value beyond annotations but is 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 concise sentences with no redundancy. The description quickly communicates the main function and return fields, efficiently using 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?
For a simple search tool without an output schema, the description adequately covers purpose and return fields. It lacks only explicit usage guidance against siblings and details like sorting, but these are minor given the tool's simplicity.
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%, with all three parameters having descriptions. The tool description adds no additional parameter details beyond the schema, so it meets the baseline for fully documented parameters.
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 the tool's function: searching the editorial corpus by query and returning specific fields. However, it does not explicitly distinguish itself from siblings like list_articles, relying instead on the verb 'search' to imply differentiation.
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 implies this tool is for free-text searching, but it does not explicitly state when to use it over list_articles or get_article, nor does it mention any exclusions or alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
cite_article1 field changedInput schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"get_article1 field changedInput schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"get_crisis_resources1 field changedInput schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"get_microsite_info1 field changedInput schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"list_articles1 field changedInput schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"search_articles1 field changedInput schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"cite_article2 fields changedInput schema / $schemaAdded value: +"http://json-schema.org/draft-07/schema#"Input schema / properties / format / descriptionPrevious value: -"Citation format. Default: ama."New value: +"Citation style (default ama)."get_article2 fields changedInput schema / $schemaAdded value: +"http://json-schema.org/draft-07/schema#"Input schema / properties / slug / descriptionPrevious value: -"Article slug, e.g. \"what-an-evaluation-actually-looks-like\"."New value: +"Article slug."get_crisis_resources1 field changedInput schema / $schemaAdded value: +"http://json-schema.org/draft-07/schema#"get_microsite_info1 field changedInput schema / $schemaAdded value: +"http://json-schema.org/draft-07/schema#"list_articles9 fields changedInput 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"search_articles6 fields changedInput schema / $schemaAdded value: +"http://json-schema.org/draft-07/schema#"Input schema / properties / limit / maximumAdded value: +50Input schema / properties / limit / minimumAdded value: +1Input schema / properties / limit / typePrevious value: -"number"New value: +"integer"Input schema / properties / qAdded value: +{
+ "description": "Alternate parameter name for `query`.",
+ "type": "string"
+}Input schema / properties / query / descriptionPrevious value: -"Free-text query. Matches title and summary."New value: +"Free-text search query."cite_articleget_articleget_crisis_resourcesget_microsite_infolist_articlessearch_articlesClinician-reviewed library on social anxiety, panic, and school refusal in adolescents.
Clinician-reviewed library on ADHD in teens — accommodations, executive function, evaluations.
Adolescent psychiatry library focused on the medication decisions parents wrestle with.
Plain-English child psychiatry library — short explainers and decision guides for parents.
Add one secure layer between your agents and this server.
