Smartschool MCP Server

get_results

Retrieve student grades and results from Smartschool. Filter by course, include teacher averages and medians, or keep it basic to reduce API calls.

Instructions

Retrieve student results/grades with detailed information.

Args: limit: Maximum number of results to return (default: 15) offset: Number of results to skip from the beginning (default: 0) course_filter: Filter results by course name (partial match, case-insensitive) include_details: Whether to fetch detailed info (teacher, average, median) - saves API calls if False

Returns: Dictionary with results list and pagination info.

Examples: - get_results() -> First 15 results with details - get_results(course_filter="Math") -> Results from courses containing "Math" - get_results(include_details=False) -> Basic info only, faster response

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No
`offset`	No
`course_filter`	No
`include_details`	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_resultsDictOutput",
+  "type": "object"
+}

First observedv0.2.0Jun 29, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With no annotations, the description carries the full behavioral burden. It discloses pagination behavior via limit/offset, notes that include_details saves API calls, and states that the return value includes a results list and pagination info, adding meaningful context beyond the schema.

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 well-structured and front-loaded with the core purpose, followed by args, returns, and examples. A few examples are somewhat redundant with the parameter list, but they add practical clarity without excessive bloat.

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?

Given the simple 4-parameter tool with an output schema present, the description covers all necessary invocation details: parameters, defaults, behavior, return shape, and performance considerations. Nothing critical is missing for an agent to call this tool correctly.

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

Parameters5/5

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

Schema description coverage is 0%, and the description fully compensates by explaining every parameter: limit, offset, course_filter's partial match/case-insensitive behavior, and include_details' trade-off of API calls for detailed fields like teacher, average, and median. It also provides concrete examples that illustrate parameter usage.

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 tool's purpose: retrieving student results/grades with detailed information. It distinguishes itself from siblings like get_courses and get_reports by naming the specific resource type, though it does not explicitly contrast itself with get_reports.

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 examples and argument descriptions imply when to use the tool, such as filtering by course or suppressing details for faster responses. However, it does not explicitly state when to prefer this over sibling tools like get_reports or get_periods, nor does it mention any 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