Skip to main content
Glama
chrischall

schoolpass-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

schoolpass_list_drivers

Read-onlyIdempotent

List authorized pickup drivers for your child's school account. Optionally include carpool memberships to see which carpools each driver belongs to.

Instructions

List the authorized pickup drivers registered on the parent account. Pass include_carpool: true to also get the carpools each belongs to — those records describe OTHER families, so on the default compact view their contact and vehicle fields are dropped (view "full" keeps them).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
viewNoResponse shape: "compact" (default) drops fields the response already carries elsewhere; "full" returns every field this server understands. compact strips image/avatar URLs from the response; "full" returns SchoolPass's payload untouched. No field projection: this server has no verified record of which SchoolPass fields matter, and inventing one would risk dropping a field a caller needs.
include_carpoolNoAlso return the carpools each driver belongs to (other families' data). Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.4
    • addedInput schema / properties / include_carpool
      Added value: +{
+  "default": false,
+  "description": "Also return the carpools each driver belongs to (other families' data). Default false.",
+  "type": "boolean"
+}
  2. 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"
  3. Changed1 schema field changedv0.4.2
    • addedInput schema / properties / view
      Added value: +{
+  "description": "Response shape: \"compact\" (default) drops fields the response already carries elsewhere; \"full\" returns every field this server understands. compact strips image/avatar URLs from the response; \"full\" returns SchoolPass's payload untouched. No field projection: this server has no verified record of which SchoolPass fields matter, and inventing one would risk dropping a field a caller needs.",
+  "enum": [
+    "compact",
+    "full"
+  ],
+  "type": "string"
+}
  4. First observedv0.2.0

TDQS

A4.7/5.0
Behavior5/5

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

The description goes well beyond the readOnlyHint and idempotentHint annotations by explaining the default compact view drops contact and vehicle fields for carpool records, that carpool records describe other families, and that view 'full' keeps those fields. This meaningfully informs the agent about response-shape behavior.

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 no filler. The first sentence states the core purpose immediately; the second packs necessary caveats about include_carpool, other families, and the compact/full view distinction without wasting words.

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 zero-required-parameter list operation with no output schema, this description is complete. It states what is returned, how the optional parameter changes the response, and what the default view strips. An agent can call this tool correctly with the information provided.

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?

The schema already documents both parameters thoroughly, so the baseline is 3. The description adds valuable cross-parameter context by linking include_carpool: true to the carpools returned and explaining how the default compact view affects those carpool records, which the schema does not explicitly state.

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 resource: 'List the authorized pickup drivers registered on the parent account.' This clearly distinguishes the tool from siblings like schoolpass_list_students, schoolpass_list_pickup_changes, and schoolpass_list_dismissal_locations.

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 provides clear context: this is for retrieving authorized pickup drivers on the parent account. It does not name alternatives or exclusion criteria, but the function and scope are unmistakable, and sibling tool names reinforce when this tool is appropriate.

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