Skip to main content
Glama
oliverhruby

EduPage MCP Server

by oliverhruby
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_meals

Read-onlyIdempotent

Retrieve the school meal menu for a given date, including breakfast, snack, lunch, afternoon snack, and dinner, and see options to choose or sign off.

Instructions

Get the meal menu for a date. Read-only. Always returns all five meal slots (breakfast, snack, lunch, afternoon_snack, dinner) — slots not published by the school are None.

Args: date_str: YYYY-MM-DD (default today). subdomain: School to query (defaults to the active subdomain).

Returns: dict: {'date', 'subdomain', 'meals': {breakfast/snack/lunch/ afternoon_snack/dinner: menus}}. Each menu carries chooseable/ordered info usable with choose_meal / sign_off_meal.

Notes: - Tries the personal ordering endpoint first; when the school hasn't enabled it, falls back to the school's public canteen menu widget.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
date_strNo
subdomainNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.6.0
    • addedInput schema / properties / date_str / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedInput schema / properties / date_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. Changed2 schema fields changedv0.5.0
    • removedInput schema / properties / include_breakfast
      Removed value: -{
-  "default": false,
-  "title": "Include Breakfast",
-  "type": "boolean"
-}
    • removedInput schema / properties / include_dinner
      Removed value: -{
-  "default": false,
-  "title": "Include Dinner",
-  "type": "boolean"
-}
  3. First observedv0.4.6

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations (which already declare read-only/idempotent/non-destructive), the description adds meaningful behavior: all five slots are always returned with unpublished ones set to None, and it discloses the fallback path from the personal ordering endpoint to the public canteen widget. This is exactly the kind of context the annotations cannot convey.

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 single-sentence purpose, then cleanly separated Args/Returns/Notes sections. No filler; every line (including the None-for-unpublished detail) earns its place.

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 supplies the return shape ({date, subdomain, meals{...}}) and the note about the menu fields usable with downstream tools, so an agent knows both how to call it and what it gets back.

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 coverage is 0%, so the description carries the full burden and does: date_str is documented as YYYY-MM-DD defaulting to today, and subdomain as defaulting to the active subdomain. Both parameters get format and default semantics absent from the schema.

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 meal menu') plus the scoping dimension ('for a date'), and routes the agent to the downstream siblings that consume the result ('choose_meal' / 'sign_off_meal'). An agent can distinguish this read tool from the meal-mutation siblings without opening any 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?

It clearly positions the tool as the read entry-point whose output feeds choose_meal/sign_off_meal, giving implied usage context. However it never states an explicit when-not or prerequisite (e.g., that you must fetch meals before choosing), so it stops short of a full 5.

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