Skip to main content
Glama
Waypoint IEP Differentiation Server

Waypoint IEP Differentiation Server

by Maliik-B

generate_teacher_prep_summary

Generates a printable one-page before-class teacher prep summary with student snapshot, top reminders, materials checklist, timed plan, risk signs, intervention scripts, and IEP data reminders.

Instructions

Generate a one-page 'before class' summary with everything a teacher needs to prepare: student snapshot (reading level, behavioral pattern, what works), top 3 things to remember, materials checklist, minute-by-minute timeline with risk levels, early warning signs and intervention scripts, and IEP data collection reminders. Designed to be printed and taped to the lesson binder.

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_teacher_prep_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
include_materials_listNoWhether to include a printable materials preparation checklist.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses the deliverable's contents in detail (snapshot, top 3, timeline with risk levels, intervention scripts, IEP reminders) and implies a printable output, but says nothing about whether anything is persisted, whether it is a pure read/generation, what data must already exist for the student, or the output format/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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded in the first clause, followed by a tightly packed content inventory and one short usage sentence. The long comma-separated inventory is dense but every element describes a distinct output section, so little is wasted.

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-boolean tool with no output schema, the description substitutes well by enumerating the returned sections. The only real gap is that no parameter identifies the student or lesson, leaving it unclear whether context is inferred from the session — a point the description could have clarified.

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 single parameter (include_materials_list) is fully documented in the schema with a type and default of true, so the schema does the heavy lifting. The description's mention of a 'materials checklist' is consistent with that flag and hints at its effect, adding mild value beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description pairs a specific verb ('Generate') with a concrete artifact ('one-page before class summary') and then enumerates its sections, so an agent knows exactly what will be produced. It does not explicitly contrast itself with near-siblings like generate_classroom_summary, which keeps it out of 5 territory.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Before class' and 'designed to be printed and taped to the lesson binder' imply the usage context (pre-lesson teacher preparation). There is no explicit when-to-use-vs-alternative routing, no statement about prerequisites, and no exclusion of cases where a sibling such as generate_lesson_modifications would be the better pick.

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