Skip to main content
Glama
oliverhruby

EduPage MCP Server

by oliverhruby
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

login

Idempotent

Authenticate to EduPage for a school, creating or replacing the server-side session for that subdomain. Use credentials, auto-detect, or session ID; handles 2FA.

Instructions

Log in to Edupage for a school. Writes: establishes (or replaces) the server-side session for that subdomain.

Args: username: EduPage account login. Falls back to EDUPAGE_USERNAME. password: Account password. Falls back to EDUPAGE_PASSWORD. subdomain: School subdomain (e.g. 'school'). Falls back to the first value of EDUPAGE_SUBDOMAINS; for method='auto' it is optional and tags the detected school's session. method: How to authenticate: - 'credentials' (default) — username/password for a known subdomain. - 'auto' — portal auto-detect of the school (formerly login_auto). - 'session' — build a session from an existing PHPSESSID cookie (formerly login_from_session); pass it in session_id. session_id: PHPSESSID cookie value, required when method='session'.

Returns: dict with logged_in status, subdomain, user_id, role and whether 2FA is pending. When two_factor_required is true, finish with two_factor_finish.

Notes: - Each login call adds/replaces that subdomain's session; call login_all to log into several schools in one call. - When EDUPAGE_SUBDOMAINS is set it is a strict allowlist: login into a school outside it is refused. - Prefer setting EDUPAGE_USERNAME / EDUPAGE_PASSWORD (and EDUPAGE_SUBDOMAINS for multi-school) — the server then logs in automatically at startup.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
methodNocredentials
passwordNo
usernameNo
subdomainNo
session_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changedv0.6.0
    • addedInput schema / properties / method / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedInput schema / properties / method / type
      Removed value: -"string"
    • addedInput schema / properties / password / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedInput schema / properties / password / type
      Removed value: -"string"
    • addedInput schema / properties / session_id / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedInput schema / properties / session_id / type
      Removed value: -"string"
    • addedInput schema / properties / subdomain / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedInput schema / properties / subdomain / type
      Removed value: -"string"
    • addedInput schema / properties / username / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedInput schema / properties / username / type
      Removed value: -"string"
  2. Changed2 schema fields changedv0.5.0
    • addedInput schema / properties / method
      Added value: +{
+  "default": "credentials",
+  "title": "Method",
+  "type": "string"
+}
    • addedInput schema / properties / session_id
      Added value: +{
+  "default": null,
+  "title": "Session Id",
+  "type": "string"
+}
  3. First observedv0.4.6

TDQS

A5/5.0
Behavior5/5

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

Annotations only cover the safety profile (readOnly=false, idempotent=true). The description goes well beyond, disclosing that each call adds/replaces a subdomain's server-side session, that EDUPAGE_SUBDOMAINS acts as a strict allowlist with refusals, and that 2FA may need two_factor_finish to complete.

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-loaded with the one-line purpose and write semantics, then cleanly sectioned into Args/Returns/Notes. Despite its length, every line conveys non-derivable information (env fallbacks, allowlist behavior, 2FA handoff) rather than restating the schema.

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?

Although there is no output schema, the description documents the return dict (logged_in, subdomain, user_id, role, 2FA-pending) and the follow-up tool for 2FA. For an auth tool with five optional params and no required fields, this is complete enough to invoke 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?

With 0% schema description coverage the description must carry the full burden, and it does: all five params are documented, including env-var fallbacks for username/password/subdomain and the required session_id value when method='session'. The method enum values are fully explained even though the schema declares no enum.

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+resource ("Log in to Edupage for a school") and immediately scopes the side effect ("establishes (or replaces) the server-side session for that subdomain"). It clearly differentiates from the sibling login_all by noting that tool handles multiple schools in one call.

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 enumerates the three mutually exclusive authentication strategies ('credentials', 'auto', 'session') with the condition that selects each, and names login_all as the alternative for multi-school login. It also advises preferring EDUPAGE_USERNAME/EDUPAGE_PASSWORD for auto-login at startup.

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