Skip to main content
Glama
Sign In
pickuppatrol-mcp

pickuppatrol-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

pup_set_default_plans

DestructiveIdempotent

Change a student's weekly default dismissal plan for chosen weekdays, or clear all defaults, so their regular school pickup method applies on dates without a specific plan.

Instructions

Change a student's weekly default dismissal plan for one or more weekdays, or clear every default. This is how the child leaves school on any date without a specific plan. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). Read pup_list_transportations first.

Input Schema

NameRequiredDescriptionDefault
daysNoWeekdays to change, as names ("Monday") or ids (1 = Sunday … 7 = Saturday)
noteNoNote for the school; required by some options
clear_allNoRemove every weekday default instead of setting one (days is ignored)
car_numberNoCar number, for options where usesCarNumbers is true; omit to keep the weekday's current number
student_idYesStudent id, from pup_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.
transportation_idNoDismissal option id from pup_list_transportations
early_dismissal_timeNoHH:MM, required when the option is an early dismissal

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.2
    • addedInput schema / properties / car_number
      Added value: +{
+  "description": "Car number, for options where usesCarNumbers is true; omit to keep the weekday's current number",
+  "type": "string"
+}
  2. Changed2 schema fields changedv1.1.0
    • removedInput schema / properties / confirm
      Removed value: -{
-  "description": "Must be true to proceed. Without this, the tool returns a preview.",
-  "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. First observedv0.1.2

TDQS

A4.4/5.0
Behavior5/5

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

Annotations mark this destructive and idempotent, but the description goes well beyond them by disclosing the entire confirmation protocol: a client prompt where supported, otherwise a phase-1 preview plus a confirmToken that must be passed back in a repeat call, referencing MCP_CONFIRM_MODE. That is exactly the kind of non-obvious, beyond-annotation behavior an agent needs.

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 purpose, then differentiation, then the confirmation mechanics, then the prerequisite. Every sentence carries information, though the confirmation sentence is dense and could be split for scanning.

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 still explains the two possible return shapes (confirmation prompt or preview + confirmToken), plus the prerequisite read call. For an 8-parameter destructive mutation tool, that is enough for an agent to call it 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?

Schema description coverage is 100%, so the baseline is 3; each parameter (days, clear_all, car_number, note, confirmToken) is already documented in the schema. The description adds the semantic link that clear_all ignores days and that omitting car_number preserves the current value only implicitly, so it does not substantially exceed the schema.

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 and resource (change a student's weekly default dismissal plan), names the two modes (per-weekday change vs. clear all), and adds the scoping sentence 'This is how the child leaves school on any date without a specific plan,' which implicitly separates it from the date-specific sibling pup_set_plan.

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 an explicit prerequisite ('Read pup_list_transportations first') and lays out the confirmation requirement before calling, which is real actionable guidance. It does not explicitly name pup_set_plan as the alternative for a specific-date override, leaving that to inference from 'any date without a specific plan.'

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