Skip to main content
Glama
chrischall

schoolpass-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

schoolpass_cancel_dismissal_change

Cancel a student's previously submitted dismissal or arrival change for a date, restoring the default schedule. Preview the change first, then confirm to actually cancel.

Instructions

Cancel a previously-submitted dismissal/arrival change for a student on a date, returning that date to its default. CONFIRM-GATED: without confirm:true it looks up the change and returns a preview of what would be cancelled, making no change. With confirm:true 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).
confirmNoMust be true to actually cancel. Without it, returns a preview only.
student_idYesStudent id (schoolpass_list_students).
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 dry-run. Optional when the date has exactly one cancellable change.

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. 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"
+}
  3. First observedv0.2.0

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false), the description discloses the two-phase behavior: without confirm it only previews and makes no change; with confirm it deletes and re-reads the calendar to verify the default state. This is rich, precise behavioral disclosure that significantly aids an agent. No contradiction with 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 two sentences with the main action and effect front-loaded, followed by the confirm-gate detail. It is concise, well-structured, and every word contributes to understanding. No fluff or redundancy.

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 cancellation tool with a confirm gate and an optional change_series_id, the description explains the complete flow: preview vs. deletion, the condition for the optional parameter, and the post-deletion verification. No output schema exists, so return values need not be explained. The description is comprehensive for an agent to invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema covers 100% of parameters with descriptions, including confirm's requirement and change_series_id's optionality. The description reinforces the confirm gate and the optionality condition but adds no new meaning beyond the schema. Baseline 3 is appropriate given full schema coverage.

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 clearly states the action (cancel), the target (previously-submitted dismissal/arrival change for a student on a date), and the outcome (returning the date to its default). It distinguishes itself from siblings like submit_dismissal_change and list_pickup_changes by focusing specifically on cancellation. The two-mode behavior (preview vs. confirmed) is also explicitly described.

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?

The description implies usage after submitting a change and explains the confirm gate requirement, which is essential. It does not explicitly name alternative tools or state when not to use it, but the context (cancelling a previously-submitted change) is clear enough for an agent to decide. The absence of explicit sibling comparison is a minor gap.

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