Skip to main content
Glama
oliverhruby

EduPage MCP Server

by oliverhruby
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_homework_material

Read-onlyIdempotent

Fetch complete homework material content and absolute attachment URLs from an EduPage superid to read assignment details the timeline summary omits.

Instructions

Full body text and attachment list of one homework/assignment material. Read-only.

Fetches the school's material-player page for superid and flattens its widget tree into plain text plus absolute attachment URLs — the timeline notification carries only a short summary, never the assignment body or the attachment list, so this is the only way to read what the assignment says.

Args: superid: Material id, taken from additional_data.superid of a notification returned by get_timeline(category='homework'). subdomain: School whose session to use (defaults to the active subdomain).

Returns: dict: {'subdomain', 'superid', 'title', 'details', 'date_from', 'date_to', 'content', 'attachments'}. Each attachment is {'name', 'url'} with an absolute URL — hand url to download_attachment to save it.

Notes: - Discover ids first: get_timeline(category='homework') (or category='assignments') and read additional_data.superid. For a whole day of homework plus everything else prefer get_day_summary. - An invalid, expired or invisible id returns an actionable error, not a stack trace. - content is plain text; an enabled student upload area is rendered as '[Student answer / file upload area]'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
superidYes
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. Addedv0.5.2

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds genuinely new behavioral context: invalid/expired ids yield an actionable error rather than a stack trace, and an enabled student upload area is rendered as a literal placeholder string. These are non-obvious traits not derivable from annotations.

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 front-loaded with a one-line summary before the Args/Returns/Notes blocks, and every sentence earns its place. It is somewhat verbose with a fairly long Returns enumeration, but the structure aids scanning rather than padding.

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?

With no output schema, the description compensates by spelling out the returned dict keys and the attachment shape ({'name','url'} with absolute URL). Combined with the discovery notes and error behavior, an agent has everything needed to call and use the result 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%, so the description carries the full burden and does so: `superid` is the material id sourced from `additional_data.superid` of a timeline notification, and `subdomain` selects the school session with an explicit default. Both parameters get meaning beyond their bare names.

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 opening line states a specific verb+resource+scope ('Full body text and attachment list of one homework/assignment material') and immediately distinguishes it from the timeline sibling by noting the timeline carries only a short summary. An agent can tell exactly what it retrieves without opening the 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 routes the agent: discover ids via `get_timeline(category='homework')`, and prefer `get_day_summary` for a whole day of homework. It also names the downstream tool (`download_attachment`) that consumes the returned URLs, giving clear when/when-not guidance.

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