Skip to main content
Glama
Waypoint IEP Differentiation Server

Waypoint IEP Differentiation Server

by Maliik-B

export_printable_materials

Bundle all lesson materials into one print-ready packet; choose clean student handouts or teacher versions with answer keys and implementation notes.

Instructions

Bundle all student materials for a lesson into a single print-ready document. Includes graphic organizers, writing scaffolds, schedule cards, pause-plan-proceed cards, and vocabulary reference sheets. Supports student mode (clean handouts for photocopying) and teacher mode (adds answer keys and implementation notes). Designed to be printed as one packet before class.

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

Input Schema

NameRequiredDescriptionDefault
modeNoStudent mode produces clean handouts. Teacher mode adds answer keys and implementation notes.student
includeNoWhich materials to include. Defaults to all. Options: graphic-organizer, writing-scaffold, schedule-card, pause-plan-proceed, vocabulary-reference, teacher-cheat-sheet.

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 behavioral burden. It discloses output form (single print-ready document), included content, and mode-specific behavior, but does not state permission requirements, whether the export mutates anything, or how the document is delivered.

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?

The description is front-loaded and tightly structured: purpose first, then included materials, then mode behavior, then printing context. Every sentence and clause adds useful meaning without unnecessary repetition.

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 export tool with no output schema, the description does a good job explaining what the output contains and how modes affect it. It leaves some gaps around exact file format or delivery mechanism, but an agent has enough context to select and call it correctly.

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 the schema already defines both parameters and their enum values. The description reinforces mode semantics (student clean handouts vs teacher answer keys and implementation notes) and lists material categories, but largely restates information already present in 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 states a specific action and output: bundling student materials into a single print-ready document. It also enumerates the included materials and mode variants, so the resource is clear. It does not explicitly differentiate itself from sibling generators such as generate_take_home or generate_sub_card, keeping it at a strong 4 rather than 5.

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?

The description implies the use case: preparing a packet before class for photocopying, with student mode for clean handouts and teacher mode for answer keys and notes. However, it gives no explicit when-to-use/when-not-to-use guidance or direction to alternatives when a single material or digital format is wanted.

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