Skip to main content
Glama
Waypoint IEP Differentiation Server

Waypoint IEP Differentiation Server

by Maliik-B

generate_progress_data_sheet

Generate a structured IEP progress data collection form that maps each goal benchmark to lesson activities, with observation checklists, rubrics, and a frustration log for quarterly reporting.

Instructions

Generate a structured IEP progress data collection form for this lesson. Maps each IEP goal benchmark to specific lesson activities, providing observation checklists, scoring rubrics, and a frustration event log. The SE teacher fills this out during or after the lesson for quarterly progress reporting. Tracks ELA benchmarks (annotation, comprehension, writing) and self-regulation benchmarks (recognition, strategy use, re-engagement).

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

Input Schema

NameRequiredDescriptionDefault
goalsNoWhich IEP goals to generate data collection for. Default: all applicable goals.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.3/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 burden and does well: it discloses the output structure (checklists, rubrics, event log), the intended consumer (SE teacher), and the downstream purpose (quarterly reporting). It does not address side effects, whether lesson context is required, or whether the form is returned vs. stored, which keeps it below a 5.

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 sentences, front-loaded with the core action and followed by output contents, audience, and tracked domains. Every sentence adds information; there is little waste, though the closing benchmark enumeration could be tightened.

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 generation tool with one optional parameter and no output schema, the description compensates well by describing what the generated artifact contains and who uses it. It leaves unstated whether the tool implicitly consumes the current lesson context or how large the output is, a small gap against the complexity of the deliverable.

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% with a single optional 'goals' array, so the baseline is 3; the description earns an extra point by explaining what the benchmark categories mean ('ELA benchmarks (annotation, comprehension, writing) and self-regulation benchmarks (recognition, strategy use, re-engagement)'). Minor gap: the enum also accepts 'math', which the description never mentions.

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

Purpose5/5

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

The description opens with a specific verb+resource pair ('Generate a structured IEP progress data collection form for this lesson') and immediately distinguishes itself from the sibling generate_* tools by naming its output artifacts: observation checklists, scoring rubrics, and a frustration event log. An agent can tell this is a progress-monitoring generator rather than a lesson-modification or summary tool.

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?

It states clear usage context: the SE teacher completes it during or after the lesson for quarterly progress reporting, which implies the right moment to invoke it. It stops short of explicit exclusions or naming an alternative tool for adjacent needs, so it lands at 4 rather than 5.

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