Smartschool MCP Server

get_schedule

Retrieve your Smartschool lesson schedule for any day by specifying a date offset from today, with 0 meaning today, 1 tomorrow, -1 yesterday.

Instructions

Retrieve the lesson schedule for a given day.

Args: date_offset: Days from today (0=today, 1=tomorrow, -1=yesterday, default: 0)

Returns: Dictionary with the lessons scheduled for the given date.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`date_offset`	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_scheduleDictOutput",
+  "type": "object"
+}

First observedv0.2.0Jun 29, 2026

TDQS

A3.9/5.0

Behavior3/5

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

With no annotations provided, the description carries the burden of disclosing behavior. It states 'Retrieve' and 'Returns: Dictionary', which implies a read-only operation and describes the output type. However, it does not disclose whether there are side effects, permission requirements, or behavior for dates with no lessons. The description is sufficient for a simple read but omits potential edge-case behaviors.

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 concise, with a clear one-sentence purpose followed by an Args/Returns breakdown. It is front-loaded and each sentence adds value. The docstring style is slightly verbose but acceptable for clarity.

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

Completeness4/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 optional parameter and no annotations, the description covers the essential behavior: retrieving a schedule and returning a dictionary. It does not detail error handling or define the structure of the returned dictionary, but given the tool's simplicity and the presence of an output schema (indicated by context), this is adequate. The description could mention behavior for invalid offsets, but that is a minor gap.

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?

The schema only provides a title and default for date_offset, with no description. The description fully explains the parameter: 'Days from today (0=today, 1=tomorrow, -1=yesterday, default: 0)'. This adds meaningful context beyond the schema, compensating for the 0% schema coverage.

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?

The description states a specific verb ('Retrieve'), a resource ('lesson schedule'), and a scope ('for a given day'). It clearly distinguishes this from siblings like get_courses and get_periods, which likely handle different data. An agent can understand its purpose without ambiguity.

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 retrieving a day's schedule and specifies date_offset semantics, but it does not explicitly mention when to use this tool versus alternatives like get_periods or get_future_tasks. There is no statement of exclusions or conditions that would route the agent appropriately.

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

Deploy Server