Skip to main content
Glama
oliverhruby

EduPage MCP Server

by oliverhruby
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

sign_off_meal

DestructiveIdempotent

Cancel an ordered meal for a specified date and meal type, releasing the booking in EduPage to avoid unwanted charges.

Instructions

Cancel an ordered meal for a date. Writes: releases the booking.

Args: date_str: YYYY-MM-DD to cancel. meal_type: 'snack' | 'lunch' | 'afternoon_snack'. subdomain: School to query (defaults to the active subdomain).

Returns: dict: {'ordered': False, meal_type, date}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
date_strYes
meal_typeYes
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

A4.2/5.0
Behavior4/5

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

Annotations already declare the write/destructive/idempotent/openWorld profile, so the bar is lower, and the description adds real context by stating "Writes: releases the booking" and showing the returned state {'ordered': False}. It does not mention permission/auth requirements or what happens if no booking exists, so it stops short of full disclosure.

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 with the action and write semantics, followed by compact Args/Returns blocks; every line is informational. The fragment "Writes: releases the booking" is slightly telegraphic, but nothing is wasted.

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 helpfully specifies the return dict, and it documents all three parameters. The gaps are error/edge-case behavior (meal not ordered, invalid date, permission failure) rather than anything needed to invoke it 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% and the schema exposes meal_type as an unconstrained string, so the description carries the full burden — and does: it supplies the YYYY-MM-DD format, the exact allowed meal_type values ('snack'|'lunch'|'afternoon_snack'), and the subdomain default behavior. This is essential information present nowhere else.

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 description gives a specific verb ("Cancel") and resource ("an ordered meal"), scoped by date, which disambiguates the otherwise opaque name sign_off_meal. This reads clearly as the inverse of the sibling choose_meal, so an agent can route without opening a schema.

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?

Usage is implied: you cancel a meal that was previously ordered for a given date. However, there is no explicit when/when-not guidance, no statement of prerequisites (e.g., a booking must already exist), and no named alternative such as choose_meal.

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