Skip to main content
Glama
Waypoint IEP Differentiation Server

Waypoint IEP Differentiation Server

by Maliik-B

generate_sub_card

Create a substitute teacher emergency card for a student with an IEP, summarizing behavior patterns, required accommodations, and shutdown strategies so any sub can respond in under two minutes.

Instructions

Generate a substitute teacher emergency card for a student with an IEP. Designed to be left in the substitute folder and read in under 2 minutes. Covers the student's behavioral pattern, legally required accommodations (simplified for someone with no IEP training), what to do if the student shuts down, and what strategies work. Optionally includes lesson-specific timing and materials notes. Subs typically receive NO IEP information -- this card fills that gap.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "generate_sub_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
include_lesson_specificsNoWhether to include lesson-specific notes (activity timing, question scaffolds). Set to false for a general-purpose card that works across any lesson.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it does disclose substantial behavior: the card's contents (behavioral pattern, simplified legal accommodations, shutdown protocol, effective strategies), its intended length/consumption time, and the effect of the optional lesson-specifics section. It never states the return format (printable file, markdown, PDF) or whether generation requires a student to be pre-selected in context, which is the main remaining behavioral gap.

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?

Purpose is front-loaded in sentence one, and each subsequent sentence adds a distinct fact (audience, contents, optional section, rationale). It is slightly denser than necessary — the contents list and the rationale sentence overlap somewhat — but there is no filler.

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 one-optional-flag generator with no output schema or annotations, the description is close to complete: it explains what is produced, for whom, and what the flag changes. It stops short of specifying the output medium and how the target student is identified given that no student parameter exists, both of which an agent would need to call this confidently.

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% and the single parameter already documents both true and false behavior, so the schema does the heavy lifting. The description adds only slight extra meaning by clarifying what lesson-specific content consists of ("timing and materials notes"), which the schema already covers as activity timing and question scaffolds.

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 first sentence gives a specific verb and a very specific artifact: "Generate a substitute teacher emergency card for a student with an IEP." The audience (substitute folder) and the distinguishing trait (read in under 2 minutes) make confusion with siblings like generate_classroom_summary or generate_teacher_prep_summary implausible without needing to name them.

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 establishes the usage context clearly: the card is meant to be left in the substitute folder and consumed in under two minutes by someone with no IEP training, justified by "Subs typically receive NO IEP information." There is no explicit when-not guidance or named alternative for overlapping needs (e.g., vs. generate_lesson_modifications), which keeps it below a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.