EduPage MCP Server

clear_student_cache

Idempotent

Clear cached student data to refresh student lists from EduPage after adding/removing students or when lookups seem outdated.

Instructions

Force refresh of cached student data. Writes: drops the local cache so the next student lookup re-fetches from EduPage. Call this after students are added/removed from a school, or if scan_students/find_student seems stale.

Args: subdomain: School whose cache to clear. Without it, clears ALL schools.

Returns: dict: {'cleared': <subdomain|'all'>, 'entries_removed': }.

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": "clear_student_cache"
  }
}

Input Schema

Name	Required	Description	Default
`subdomain`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.6.0Oct 2, 2026
- addedInput schema / properties / subdomain / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedInput schema / properties / subdomain / type
```
Removed value: -"string"
```
First observedv0.4.6Sep 9, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations declare readOnlyHint=false and destructiveHint=false, but the description adds the concrete behavior: it drops the local cache so the next lookup re-fetches from EduPage. This explains the side effect precisely – a local, non-destructive mutation – which the annotations alone do not convey. Also documents the return shape.

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?

Front-loads the action and effect, then gives scope and the crucial default behavior, then return format. Every sentence adds necessary information without padding.

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?

Complete for a single-parameter mutation tool with no output schema. It covers the side effect, default scope, triggers, and return keys. Minor deduction because there is no output schema and the description still supplies the return shape, which is helpful but could be considered beyond strict necessity; however, nothing critical is missing.

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 coverage is 0%, so the description must carry the full parameter burden. It does: 'subdomain: School whose cache to clear. Without it, clears ALL schools.' This is essential because omitting subdomain triggers a global cache clear, a high-impact behavior not evident from the bare 'string/null' schema.

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?

Uses a specific verb+resource ('Force refresh of cached student data') and clarifies it is a cache write, not a read. Distinguishes clearly from siblings like scan_students and find_student by naming them as stale-data indicators.

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

Usage Guidelines5/5

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

Explicitly says when to call it – after students are added/removed, or if scan_students/find_student seems stale. No ambiguity about appropriate timing relative to the read tools.

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