Skip to main content
Glama
oliverhruby

EduPage MCP Server

by oliverhruby
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_next_ringing_time

Read-onlyIdempotent

Find out when the next school bell rings and whether it's a break or lesson. Provide a start time and school subdomain, or default to now and the active school.

Instructions

Get the type (break/lesson) and time of the next school-bell ringing. Read-only.

Args: date_time_str: ISO datetime to search onward from (default: now). subdomain: School to query (defaults to the active subdomain).

Returns: Serialized ringing: type (break/lesson) and time.

Notes: - See get_periods for the full bell schedule.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
subdomainNo
date_time_strNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.6.0
    • addedInput schema / properties / date_time_str / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedInput schema / properties / date_time_str / type
      Removed value: -"string"
    • 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.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), and the description's 'Read-only.' largely restates that. It does add non-redundant behavior: the search starts from the given datetime or now, the school defaults to the active subdomain, and the return payload is described. Missing handling for time zones/no-more-ringings keeps this from 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose sentence is front-loaded, followed by tight Args/Returns/Notes blocks with no filler. Every line either documents a parameter, the return shape, or the sibling relationship.

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 supplies the return shape (serialized ringing with type and time), both parameter meanings and defaults, and a pointer to get_periods. It is essentially complete for a two-optional-param read tool, with only edge cases (no ringing after the given time, time-zone semantics) unaddressed.

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 carries the full burden and does so: date_time_str is documented as an ISO datetime searched onward from (default: now) and subdomain as the school to query (defaults to active subdomain). Both parameters gain meaning absent from the bare schema, though the ISO format variant/time-zone expectation is unspecified.

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 ('get the type and time of the next school-bell ringing') and enumerates the two return values (type: break/lesson, time). It also names the sibling get_periods as the source of the full schedule, so an agent can separate the two 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 Guidelines4/5

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

The Notes section explicitly routes the agent to get_periods for the complete bell schedule, which implies this tool is for the single next ringing. That is clear contextual guidance, but there is no explicit when-not condition (e.g., what happens when no further ringing exists on the given date).

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