Skip to main content
Glama
chrischall

schoolpass-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

schoolpass_submit_dismissal_change

Destructive

Submit a student's arrival or dismissal change for one date, such as a new carpool, early dismissal, absence, or late arrival. Confirm the preview to apply it.

Instructions

Submit a dismissal/arrival change for a student on a single date — send them to a different dismissal location or carpool, mark early dismissal / late arrival / absent, etc. 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 submits and then re-reads the calendar to show the change landed (verified:true); if the re-read fails or does not show it yet the result is verified:false — the change WAS submitted, so do not resubmit; re-read the calendar instead. Get student_id from schoolpass_list_students and move_to_id from schoolpass_list_dismissal_locations (a dismissal location id) or the student calendar (a carpool moveToId).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYesThe date to change (YYYY-MM-DD).
notesNoOptional note attached to the change.
ad_typeNoWhich side of the day: arrival, departure (default), or both.departure
move_to_idNoTarget dismissal location id (schoolpass_list_dismissal_locations) or carpool id. Required for carpool and bus moves (enforced); supply it for activity/location moves too.
student_idYesStudent id (schoolpass_list_students).
bus_stop_idNoBus stop id for a bus move. The app sends this field on every submit, but no bus change has been captured live, so its effect is UNVERIFIED — see docs/SCHOOLPASS-API.md.
change_typeYesThe kind of change.
time_of_dayNoOptional time of day for the change (e.g. "14:30").
will_returnNoWhether the student will return the same day (for early dismissal).
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.
pickup_dropoff_personNoOptional name of the person picking up / dropping off.

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. Changed2 schema fields changedv1.0.4
    • removedInput schema / properties / confirm
      Removed value: -{
-  "description": "Must be true to actually submit. Without it, returns a dry-run 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. Changed2 schema fields changedv0.3.1
    • addedInput schema / properties / bus_stop_id
      Added value: +{
+  "description": "Bus stop id for a bus move. The app sends this field on every submit, but no bus change has been captured live, so its effect is UNVERIFIED — see docs/SCHOOLPASS-API.md.",
+  "exclusiveMinimum": 0,
+  "maximum": 9007199254740991,
+  "type": "integer"
+}
    • changedInput schema / properties / move_to_id / description
      Previous value: -"Target dismissal location id (schoolpass_list_dismissal_locations) or carpool id. Required for carpool/bus/location moves."New value: +"Target dismissal location id (schoolpass_list_dismissal_locations) or carpool id. Required for carpool and bus moves (enforced); supply it for activity/location moves too."
  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?

Goes well beyond the destructiveHint/openWorldHint annotations: it discloses the elicitation-vs-preview two-step confirmation contract, that phase one makes no change, how the confirmToken is bound to previewed arguments and the day as read, and that a stale day is refused with a fresh preview. It also explains verified:true/false and warns not to resubmit when verification fails.

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-loads the purpose and the confirmation model, then the verification semantics, then id sourcing — a logical order with dense, information-bearing sentences. It is long and somewhat repetitious around the confirmToken/verified behavior, but little is pure padding.

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?

For a destructive, open-world mutation with no output schema and 11 parameters, the description covers the full lifecycle: id sourcing, confirmation gating, submission, and post-write re-read verification including the failure interpretation. Nothing essential for correct invocation 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 description coverage is already 100%, so the baseline is 3, but the description adds cross-tool provenance for student_id and move_to_id and clarifies confirmToken usage (never on first call, never invented) beyond the schema's note. It does not add syntax detail for the remaining optional fields, 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+resource (submit a dismissal/arrival change for a student on a single date) and enumerates the concrete change kinds it covers (location, carpool, early dismissal, late arrival, absent). The 'single date' scope distinguishes it from list_pickup_changes and its inverse sibling cancel_dismissal_change.

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?

Explains the confirm-gated invocation flow in detail and points to the sibling tools that source required ids (schoolpass_list_students for student_id, schoolpass_list_dismissal_locations or the calendar for move_to_id). It does not explicitly state when to prefer this over cancel_dismissal_change or list_pickup_changes, so exclusions are absent.

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