Skip to main content
Glama
Waypoint IEP Differentiation Server

Waypoint IEP Differentiation Server

by Maliik-B

match_accommodations

Maps IEP accommodations to specific lesson moments and produces a matrix showing when and how to implement each during a 45-minute lesson, with optional self-regulation checkpoints.

Instructions

Map each IEP accommodation to specific moments in the lesson. Produces a concrete accommodation-activity matrix showing exactly WHEN and HOW each legally mandated accommodation should be implemented during the 45-minute lesson. Optionally includes proactive self-regulation checkpoints based on the student's behavioral pattern (frustration -> avoidance -> shutdown).

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": "match_accommodations"
  }
}

Input Schema

NameRequiredDescriptionDefault
include_self_regulation_checkpointsNoWhether to include proactive self-regulation checkpoint recommendations based on the student's behavioral pattern.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description must carry behavioral disclosure. It usefully discloses the output artifact (a matrix showing WHEN and HOW each accommodation applies within a 45-minute lesson) and optional checkpoint behavior, but leaves prerequisites, data dependencies, and side effects unspecified.

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?

Three front-loaded sentences with no filler; each sentence contributes the mapping action, the output matrix, timing context, or the optional checkpoint trigger. It is appropriately sized for the tool's complexity.

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

Completeness3/5

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

Because there is no output schema, the description appropriately explains the return artifact, and the single optional parameter is covered. However, with no annotations and no required parameters, it does not state what lesson or student context it reads or what happens if accommodations are missing.

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?

Schema coverage is 100% and the boolean is fully documented there. The description adds value by naming the concrete behavioral pattern ('frustration -> avoidance -> shutdown') that justifies the checkpoint option, giving meaning 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 first sentence states a specific verb ('Map') and resource ('each IEP accommodation to specific moments in the lesson'), and the second names the concrete deliverable (accommodation-activity matrix). It does not explicitly distinguish itself from sibling tools such as check_accommodation_compliance, so it falls short of a 5.

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

Usage Guidelines2/5

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

The description gives no guidance on when to call this tool instead of alternatives, nor any prerequisites or exclusions. The optional checkpoint flag implies a use case but provides no routing guidance.

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