Skip to main content
Glama
Waypoint IEP Differentiation Server

Waypoint IEP Differentiation Server

by Maliik-B

check_accommodation_compliance

Review lesson plans against IEP accommodations to generate a compliance checklist with YES/PARTIAL/NEEDS PLAN flags, risk levels, and gap recommendations.

Instructions

Review the lesson plan against all IEP accommodations and produce a compliance checklist. Flags accommodations as YES/PARTIAL/NEEDS PLAN with risk levels. Includes lesson-specific risk assessment (high-risk moments for the student), IEP goal alignment mapping, and specific recommendations for any gaps. Important because IEP accommodations are legally binding.

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

Input Schema

NameRequiredDescriptionDefault
include_recommendationsNoWhether to include specific recommendations for addressing any gaps.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

Without annotations, the description carries the full burden, and it does disclose the output structure and classification scheme well. However, it never states what input state it requires (whether the lesson plan and accommodations set come from prior calls like match_accommodations), whether the review is read-only, or whether it persists anything, which are the behaviors an agent most needs to know.

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?

Four short sentences, front-loaded with the core action and followed by the outputs. The final sentence about legal binding is motivational rather than operational, but it is brief and does establish why compliance gaps matter.

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?

With no output schema and no annotations, the description does a reasonable job enumerating the return contents and scoring categories. It still leaves the input provenance and any prerequisite setup unstated, which is a meaningful gap for a tool with no visible input for the lesson plan or IEP data.

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?

There is a single optional boolean, and the schema documents it fully at 100% coverage, so the schema does the work. The description's mention of 'specific recommendations for any gaps' is consistent with include_recommendations but adds no new constraint or default behavior beyond what the schema states.

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 gives a specific verb and resource: review a lesson plan against IEP accommodations and produce a compliance checklist, then names concrete outputs (YES/PARTIAL/NEEDS PLAN flags, risk levels, goal alignment, recommendations). An agent knows exactly what this tool produces, but nothing in the text distinguishes it from the sibling match_accommodations or generate_lesson_modifications, so the boundary must be inferred.

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?

There is no explicit when-to-use or when-not-to-use guidance and no mention of alternatives such as match_accommodations for the matching step. The clause 'IEP accommodations are legally binding' conveys stakes but not the triggering condition for calling this tool instead of a sibling.

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