Skip to main content
Glama
chrischall

schoolpass-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

schoolpass_cancel_dismissal_change

Destructive

Cancel a previously submitted school dismissal or arrival change for a student on a specific date, reverting that day to its default schedule. Confirmation is required before the change is removed.

Instructions

Cancel a previously-submitted dismissal/arrival change for a student on a date, returning that date to its default. CONFIRM-GATED: a client that supports MCP elicitation gets a confirmation prompt; otherwise the first call makes NO change and returns a preview (the child by name, the date, the change, the exact request) plus a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). The token is bound to the previewed arguments and to the day as it was read, so a day that changed in between is refused with a fresh preview. Once confirmed it deletes the change and re-reads the calendar to confirm the day is back to default.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYesThe date whose change should be cancelled (YYYY-MM-DD).
student_idYesStudent id (schoolpass_list_students).
confirmTokenNoONLY for the two-step confirmation fallback (a client without MCP elicitation). The confirmToken from this same tool's phase-1 "confirmation-required" response, passed back ONLY after the user has seen that preview and explicitly approved it in chat — never on the first call, never invented, never reused. Call again with the same arguments. Ignored when the client supports elicitation.
change_series_idNoWhich change to cancel, when the date carries more than one. Get it from the student calendar (changeSeriesId) or from this tool's preview. Optional when the date has exactly one cancellable change.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.0.6
    • addedInput schema / properties / date / format
      Added value: +"date"
    • changedInput schema / properties / date / pattern
      Previous value: -"^\\d{4}-\\d{2}-\\d{2}$"New value: +"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))$"
  2. Changed3 schema fields changedv1.0.4
    • changedInput schema / properties / change_series_id / description
      Previous value: -"Which change to cancel, when the date carries more than one. Get it from the student calendar (changeSeriesId) or from this tool's dry-run. Optional when the date has exactly one cancellable change."New value: +"Which change to cancel, when the date carries more than one. Get it from the student calendar (changeSeriesId) or from this tool's preview. Optional when the date has exactly one cancellable change."
    • removedInput schema / properties / confirm
      Removed value: -{
-  "description": "Must be true to actually cancel. Without it, returns a preview only.",
-  "type": "boolean"
-}
    • addedInput schema / properties / confirmToken
      Added value: +{
+  "description": "ONLY for the two-step confirmation fallback (a client without MCP elicitation). The confirmToken from this same tool's phase-1 \"confirmation-required\" response, passed back ONLY after the user has seen that preview and explicitly approved it in chat — never on the first call, never invented, never reused. Call again with the same arguments. Ignored when the client supports elicitation.",
+  "type": "string"
+}
  3. Changed1 schema field changedv1.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  4. Changed1 schema field changedv0.3.1
    • addedInput schema / properties / change_series_id
      Added value: +{
+  "description": "Which change to cancel, when the date carries more than one. Get it from the student calendar (changeSeriesId) or from this tool's dry-run. Optional when the date has exactly one cancellable change.",
+  "exclusiveMinimum": 0,
+  "maximum": 9007199254740991,
+  "type": "integer"
+}
  5. First observedv0.2.0

TDQS

A4.6/5.0
Behavior5/5

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

Far exceeds the annotations (destructiveHint, non-idempotent, openWorld), which only signal that it mutates. The description discloses the confirm-gating interaction model, that phase 1 makes NO change, the exact preview payload, that the token is bound to the previewed arguments and the day as read, that a changed day is refused with a fresh preview, and that the calendar is re-read afterward to verify the default.

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?

A single dense paragraph, but the core verb+effect is front-loaded and nearly every clause carries operationally relevant information (confirmation phases, token rules, refusal behavior). It is longer than typical but not padded.

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?

No output schema exists, and the description compensates by specifying what phase 1 returns (child by name, date, change, exact request, confirmToken). For a destructive, confirm-gated mutation with four parameters, nothing an agent needs to call it correctly is missing.

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 100%, so the 3 baseline applies, but the description adds meaning beyond the field docs: it explains the token's role and binding in the confirmation lifecycle and why change_series_id is needed only when a date carries multiple changes. It does not restate the date/student_id formats, which the schema already covers.

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 (cancel) and resource (a previously-submitted dismissal/arrival change) plus the effect (returns the date to its default). An agent can immediately distinguish this from the sibling schoolpass_submit_dismissal_change 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?

Gives clear when-to-use context and, unusually, explains the two invocation modes (elicitation-capable clients vs. the two-step preview/confirmToken fallback) so the agent knows when a second call is required. It stops short of naming sibling alternatives (e.g. submit_dismissal_change, get_calendar) or stating exclusions.

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