Skip to main content
Glama
Waypoint IEP Differentiation Server

Waypoint IEP Differentiation Server

by Maliik-B

generate_lesson_modifications

Generates UDL-aligned instructional modifications for a lesson activity, grounded in curriculum content and IEP goals, so teachers get actionable differentiation for students with IEPs.

Instructions

Generate specific, actionable instructional modifications for a lesson activity. Modifications are organized using UDL framework (Engagement, Representation, Action & Expression) and grounded in both the curriculum content and IEP. Returns a structured prompt with full student context, relevant IEP goals, accommodations, lesson content, and modification instructions for Claude to reason about.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "activity_name": "<activity_name>"
    },
    "name": "generate_lesson_modifications"
  }
}

Input Schema

NameRequiredDescriptionDefault
focus_areasNoOptional: specific UDL principles or IEP areas to focus on. If omitted, all areas are addressed.
activity_nameYesWhich lesson activity to generate modifications for. Use 'full-lesson' for comprehensive modifications across all activities.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/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 behavioral burden and does disclose a crucial non-obvious trait: the tool returns a 'structured prompt' containing student context, IEP goals, accommodations, and lesson content for Claude to reason over, rather than finished modifications. That distinction prevents a wrong assumption about the return. It omits permissions/read-only status and any indication of size or truncation of the returned context, so it is strong but not complete.

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 before the return-value detail, and no filler. The second sentence is dense but every clause adds information about what comes back; a slightly clearer split of the UDL organization vs. return-payload content would improve it marginally.

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 two-parameter tool with full schema coverage and no output schema, the description covers the essentials, including an explanation of the returned prompt contents, which is necessary given the absent output schema. The remaining gap is the lack of any stated prerequisite (student/IEP context must be available) or guidance on what to do with the returned prompt afterwards.

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 coverage is 100%, so both parameters are already documented, and the description earns only baseline credit. It does map the UDL framing (Engagement, Representation, Action & Expression) loosely onto the focus_areas parameter, but it lists only three of the five enum values and omits 'accommodations' and 'self-regulation', which could subtly mislead about available focus values.

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?

States a specific verb and resource: 'Generate specific, actionable instructional modifications for a lesson activity.' The resource (lesson activity modifications, UDL-organized) is distinct from the sibling set, which generates summaries, sub cards, take-home materials, or compliance checks. It stops short of naming a sibling or contrast case, so it is clear but not fully differentiated.

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?

Usage context is implied by references to curriculum content and IEP grounding, but there is no explicit when-to-use statement, no stated prerequisites (e.g. that IEP data must exist for the student), and no exclusions or alternatives such as scaffold_question or check_accommodation_compliance. The agent must infer the selection rule from the resource name alone.

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