Skip to main content
Glama
oliverhruby

EduPage MCP Server

by oliverhruby
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_periods

Read-onlyIdempotent

Fetch the bell schedule for a school, returning each period with its start and end time. Specify a subdomain to query another school.

Instructions

Get the bell schedule (periods with start/end times). Read-only.

Args: subdomain: School to query (defaults to the active subdomain).

Returns: dict: {'periods': [{'starttime', 'endtime'}, ...]}.

Notes: - Combine with get_next_ringing_time for live bell timing.

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

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive, so the extra 'Read-only.' line repeats structured data. But the description adds genuine value beyond annotations by disclosing the return structure ({'periods': [{'starttime','endtime'}]}) and cross-tool composition. No behavioral gaps of consequence remain.

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?

Front-loaded purpose sentence, then clearly delineated Args/Returns/Notes sections. Every line earns its place and there is no filler. Slightly more verbose than a single-line ideal but structurally clean.

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?

With no output schema, the description appropriately documents the return shape, and with a single optional parameter it explains the default. An agent has enough to call and consume the result correctly; only minor gaps around alternative-tool selection remain.

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 coverage is 0%, so the description must carry parameter meaning. It does: 'subdomain: School to query (defaults to the active subdomain)' explains both the semantic (school selector) and the default behavior, which the schema only shows as default=null without explanation.

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?

States a specific verb and resource with clarifying scope: 'Get the bell schedule (periods with start/end times).' The parenthetical disambiguates it from timetable siblings. It names get_next_ringing_time as a companion but doesn't explicitly differentiate from other schedule tools like get_timetable.

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 Notes section gives a useful composition hint ('Combine with get_next_ringing_time for live bell timing'), which implies intended usage. However, it does not state when to prefer this over alternatives like get_timetable, nor any when-not conditions. Usage is only implied.

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