Skip to main content
Glama
oliverhruby

EduPage MCP Server

by oliverhruby
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

switch_to_parent

Idempotent

Restore the parent account session after switching to a child, so subsequent tools operate as the parent again.

Instructions

Switch the session back to the parent account (parent accounts only). Writes: changes which account subsequent tools operate as.

Args: subdomain: School whose session to restore (defaults to the active).

Returns: dict: {'switched_to_parent': True, 'user_id': ...}.

Notes: - Pair with switch_to_student; only relevant after a parent session was switched to a child.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
subdomainNo

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly=false and idempotent=true, but the description adds meaningful context beyond them: the write's actual effect ('changes which account subsequent tools operate as') and the return payload. It doesn't cover failure modes (e.g., calling when not switched), which keeps it short of a 5.

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?

Well-structured with labeled sections (purpose, Writes, Args, Returns, Notes) and the core purpose front-loaded. Slightly longer than strictly necessary, but each section adds usable information.

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?

There is no output schema, so the 'Returns' section is genuinely useful. The description covers the write effect, the sibling relationship, the argument, and the return shape. Only error/precondition-failure behavior is left unspecified.

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?

Schema description coverage is 0%, so the description must carry the param. It explains the single 'subdomain' arg as 'School whose session to restore' and its default behavior ('defaults to the active'), matching the null default. Clear and sufficient for one parameter.

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?

States a specific verb and resource ('Switch the session back to the parent account') with a clear scope qualifier ('parent accounts only'). An agent can distinguish it from switch_to_student without opening either schema.

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 names the paired alternative ('Pair with `switch_to_student`') and the precondition that selects it ('only relevant after a parent session was switched to a child'). The 'parent accounts only' qualifier also acts as an exclusion, leaving little to inference.

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

Deploy Server

Other Tools