Psychiatry for Teens (Clinician)

List articles

list_articles

Read-only

Paginated list of articles from Psychiatry for Teens. Returns title, slug, summary, and URL.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_articles"
  }
}

Input Schema

Name	Required	Description	Default
`page`	No	Page number (1-indexed).
`limit`	No	Max results per page (default 30, max 100).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJul 31, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

Changed9 schema fields changedMay 9, 2026
- addedInput schema / $schema
```
Added value: +"http://json-schema.org/draft-07/schema#"
```
- changedInput schema / properties / limit / description
```
Previous value: -"Page size (default 30, max 100)."New value: +"Max results per page (default 30, max 100)."
```
- addedInput schema / properties / limit / maximum
```
Added value: +100
```
- addedInput schema / properties / limit / minimum
```
Added value: +1
```
- changedInput schema / properties / limit / type
```
Previous value: -"number"New value: +"integer"
```
- changedInput schema / properties / page / description
```
Previous value: -"Page number (default 1)."New value: +"Page number (1-indexed)."
```
- addedInput schema / properties / page / maximum
```
Added value: +9007199254740991
```
- addedInput schema / properties / page / minimum
```
Added value: +1
```
- changedInput schema / properties / page / type
```
Previous value: -"number"New value: +"integer"
```
First observedApr 26, 2026

TDQS

A4.1/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The readOnlyHint annotation already signals a safe read operation; the description adds that results are paginated and include specific fields (title, slug, summary, URL). This is useful behavioral context, though ordering and total-count behavior are not disclosed. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence that immediately states operation and scope. All words add value; no fluff. Front-loaded 'Paginated list' makes purpose clear.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a low-complexity list tool with fully described optional parameters and a readOnly annotation, this description is adequate. It names the resource source and return fields, compensating for the lack of output schema. No critical gaps for invoking the tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers both page and limit with clear descriptions (1-indexed page, max results per page, default 30, max 100), so coverage is high. The description doesn't add parameter semantics beyond the pagination concept, but the schema handles it. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly identifies a paginated listing operation for articles from Psychiatry for Teens. The verb 'list' and resource 'articles' distinguish it from siblings like get_article and search_articles. Also describes returned fields, reinforcing purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Description implies use for browsing or fetching all articles in pages, but doesn't explicitly state when to choose it over search_articles or when not to use it. No alternatives or exclusions are mentioned. The pagination hint provides limited context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Psychiatry for Teens (Clinician) tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?