One U Education

List my planning dossiers

list_planning_dossiers

Read-onlyIdempotent

List only this connected account’s dossiers. Reuse next_cursor unchanged; anonymous website dossiers are separate. Requires the authenticated One U Education account and declared planning scope; credentials and user identity are never tool arguments.

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_planning_dossiers"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`cursor`	No

Output Schema

Name	Required	Description	Default
`msg`	Yes
`code`	Yes
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 31, 2026

TDQS

B3.4/5.0

Behavior4/5

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

Beyond the read-only and idempotent annotations, the description adds meaningful behavior: results are limited to the connected account, anonymous website dossiers are separate, authentication and declared planning scope are required, and credentials are never passed as arguments. It does not contradict the supplied annotations.

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

Conciseness4/5

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

The description is short and front-loads the key scoping statement. The authentication sentence is useful and the anonymous-dossier distinction is efficient. The cursor naming mismatch slightly undermines clarity.

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

Completeness3/5

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

The definition covers the important behavioral context: read-only listing, account scoping, authentication, and separation from anonymous dossiers. With an output schema present, return details need not be described. However, it omits any explanation of the limit parameter and misnames the cursor parameter, leaving notable gaps for a tool with 0% schema description coverage.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must explain the two parameters. It gives cursor reuse guidance but calls it 'next_cursor' while the actual input parameter is named 'cursor', creating a naming mismatch. The limit parameter receives no explanation at all.

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

Purpose4/5

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

The description states a specific verb and resource: listing the connected account's planning dossiers. It also distinguishes the tool's scope from anonymous website dossiers. However, it does not explicitly distinguish this tool from sibling list tools such as list_planning_calculations.

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?

The description implies usage for the authenticated account only and notes that anonymous website dossiers are separate. It also states the authentication and planning-scope prerequisites. It does not explicitly say when to choose this tool over a sibling listing tool.

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

All One U Education 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?