Skip to main content
Glama
Waypoint IEP Differentiation Server

Waypoint IEP Differentiation Server

by Maliik-B

generate_classroom_summary

Creates a classroom-at-a-glance summary for lessons with multiple IEP students, showing accommodation overlaps, materials prep, priority timeline, and teacher coordination notes.

Instructions

Generate a classroom-at-a-glance summary for a teacher managing IEP students in one lesson. Shows accommodation overlap matrix (which accommodations are shared), materials preparation list (shared vs. individualized), minute-by-minute priority timeline (who needs support when), teacher coordination notes (SE teacher vs. gen ed teacher roles), and an end-of-lesson decision tree. Designed for classes with multiple IEP students.

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

Input Schema

NameRequiredDescriptionDefault
focusNoWhich aspect to focus on. 'accommodations' shows overlap matrix, 'materials' shows shared vs. individual materials, 'timeline' shows minute-by-minute priority, 'all' includes everything.all

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, and it does disclose the full output composition, which is genuinely useful. However, it never states whether this is a pure read/compute operation or whether anything is persisted, nor what preconditions must hold (e.g., the lesson must already have IEP students and accommodation data) or how large/slow the output is for a multi-student class.

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?

Two sentences, front-loaded with the purpose and audience, then a compact enumeration of deliverables. The five-item list is dense but each item is distinct information; minor redundancy exists between the enumerated sections and the 'focus' enum values.

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?

With no output schema, the description correctly takes on the job of explaining return content and does so thoroughly, and the single optional parameter is fully covered by the schema. The remaining gap is behavioral: no annotations means prerequisites, side effects, and read-vs-write semantics are unstated.

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 'focus' enum is fully documented in-schema, so the baseline is 3. The description's restatement of accommodations/materials/timeline maps onto the same enum values without adding new syntax, defaults, or interaction detail, so it adds little 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 opens with a specific verb and resource ('Generate a classroom-at-a-glance summary') and then enumerates the five artifacts produced (overlap matrix, materials list, priority timeline, coordination notes, decision tree), which functionally separates it from narrower siblings like generate_teacher_prep_summary or generate_progress_data_sheet. It never names an alternative explicitly, so sibling differentiation is inferred rather than stated.

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?

Clear usage context is given: 'for a teacher managing IEP students in one lesson' and 'Designed for classes with multiple IEP students,' which tells the agent when this tool is a fit. There are no exclusions and no pointers to the nine sibling tools, so an agent facing an overlapping request (e.g., single-student prep) gets no routing guidance.

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