Skip to main content
Glama
chrischall

schoolpass-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

schoolpass_submit_dismissal_change

Submit a one-day dismissal/arrival change for a student. Preview it as a dry run, then confirm to apply and verify the calendar update.

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: without confirm:true it makes no change and returns a dry-run preview of the exact request. With confirm:true it submits and then re-reads the calendar to show the change landed. 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
confirmNoMust be true to actually submit. Without it, returns a dry-run preview only.
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).
pickup_dropoff_personNoOptional name of the person picking up / dropping off.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
  2. 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."
  3. First observedv0.2.0

TDQS

A4.7/5.0
Behavior5/5

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

Beyond annotations (readOnlyHint:false, openWorldHint:true), the description explains the confirm gate, the no-op dry-run behavior, and the post-submit re-read of the calendar to verify the change landed. This is meaningful behavioral context about side effects and verification, and it does not contradict the annotations.

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 description is three sentences, front-loads the core action, then gives the confirm-gate behavior and ID sourcing. No sentence is filler; the 'etc.' enumerates scope without bloating the text.

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 an 11-parameter, no-output-schema mutation tool, it is complete enough: core action, change types, safety gate, verification behavior, and ID lookup dependencies are all present. The schema handles remaining parameter-level details, and the returned behavior is described (dry-run preview vs calendar re-read).

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?

With 100% schema coverage the baseline is 3, and the description adds a useful cross-tool sourcing rule: student_id from schoolpass_list_students and move_to_id from schoolpass_list_dismissal_locations, or a carpool moveToId from the student calendar. The confirm and move_to_id semantics are mostly restated from the schema, so the added value is moderate but real.

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 opens with a specific verb and object—'Submit a dismissal/arrival change for a student on a single date'—and enumerates concrete change types such as different location/carpool, early dismissal, late arrival, and absent. It is semantically distinct from the sibling schoolpass_cancel_dismissal_change, so an agent can identify this tool without opening the 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 states when dry-run vs actual submission occurs ('without confirm:true... returns a dry-run preview... With confirm:true... submits'), which tells the agent how to safely explore. It also gives data-dependency guidance by pointing to schoolpass_list_students and schoolpass_list_dismissal_locations as sources for IDs. It does not explicitly name exclusions relative to the cancellation sibling, but the submit/cancel split is clear enough.

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