Smartschool MCP Server

get_planned_elements

Fetch upcoming assignments and to-dos from Smartschool planner for a specified number of days ahead, returning dates, courses, and assignment types.

Instructions

Retrieve planned assignments and to-dos from the Smartschool planner.

Args: days_ahead: Number of days ahead to fetch (default: 34)

Returns: Dictionary with planned elements including dates, courses, and assignment types.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`days_ahead`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.3.0Sep 23, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "title": "get_planned_elementsDictOutput",
+  "type": "object"
+}

First observedv0.2.0Jun 29, 2026

TDQS

B3.2/5.0

Behavior2/5

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

Annotations are absent, so the description must carry the full burden of behavioral disclosure. While 'retrieve' implies a read-only operation, it does not explicitly state this, nor does it mention auth needs, rate limits, pagination, or any side effects. The return-type summary adds a little context but does not compensate for the missing safety profile.

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?

The description is concise and well-structured: a one-sentence purpose statement followed by clear 'Args' and 'Returns' sections. Every sentence adds value and there is no redundant or filler content.

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?

For a simple tool with one parameter and an output schema, the description covers the basic invocation. However, it lacks comparative context with sibling tools and explicit behavioral notes, leaving an agent uncertain about when this tool is the preferred choice.

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

Parameters4/5

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

With only 0% schema description coverage, the description effectively explains the sole parameter: 'days_ahead: Number of days ahead to fetch (default: 34).' This adds meaningful semantic information beyond the raw schema, though it could be slightly more detailed about range or behavior.

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 clearly states the action and resource: 'Retrieve planned assignments and to-dos from the Smartschool planner.' This distinguishes the core function, but it does not explicitly differentiate from similar siblings like get_future_tasks, so it falls short of a 5.

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

Usage Guidelines2/5

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

No guidance is given on when to use this tool versus alternatives such as get_future_tasks or get_schedule. The description provides no contextual cues about selection criteria, exclusions, or prerequisites.

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

Deploy Server