Skip to main content
Glama
chrischall

schoolpass-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

schoolpass_list_dismissal_locations

Read-onlyIdempotent

Get the school's dismissal locations with their IDs to use in dismissal change requests. Lists car line, bus, aftercare, walkers, and more.

Instructions

List the school’s dismissal locations (car line, bus, aftercare, walkers, etc.) with their ids — the vocabulary a dismissal change refers to.

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.

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

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint. The description adds the behavioral context that the result serves as the reference vocabulary for dismissal changes, which is valuable beyond the annotations. It also confirms the output includes ids, giving a hint about the return shape.

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?

One sentence, front-loaded with the core purpose, followed by a clarifying clause about its role in dismissal changes. Every word earns its place; no fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple list tool with no output schema, the description conveys the essential facts: it lists locations and their ids, and it is the vocabulary for dismissal changes. It does not specify the exact response structure, but given the simplicity and the annotations, this is sufficient. It could mention if it returns only active locations, but that is a minor gap.

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 single parameter 'view' is fully documented in the input schema with a detailed description of compact vs full behavior. Schema coverage is 100%, so the description does not need to repeat parameter details. The tool description adds nothing about parameters, but the schema carries the load, meeting the baseline.

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 states a specific verb (List) and resource (dismissal locations), and clarifies the output includes ids. It also explicitly ties the tool to the dismissal-change vocabulary, distinguishing it from sibling list tools like list_students or list_drivers.

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 context by stating 'the vocabulary a dismissal change refers to', which signals it should be used before submitting or canceling a dismissal change. However, it doesn't explicitly state when not to use it or name alternatives, leaving some inference needed.

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