Skip to main content
Glama
Waypoint IEP Differentiation Server

Waypoint IEP Differentiation Server

by Maliik-B

generate_take_home

Generate a modified take-home version of unfinished classwork with text excerpts, reduced-scope questions, sentence starters, word banks, and an optional parent note for students with low stamina.

Instructions

Generate a modified take-home version of classwork the student didn't finish. Includes relevant text excerpts (so the student doesn't need the full article at home), reduced-scope questions, sentence starters, word banks, and an optional parent/guardian note explaining the assignment and how to help. Designed for students with low stamina or who shut down during independent practice.

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": {
      "unfinished_items": "<unfinished_items>"
    },
    "name": "generate_take_home"
  }
}

Input Schema

NameRequiredDescriptionDefault
reduced_scopeNoWhether to reduce the scope of open-ended questions for independent completion (e.g., claim + 1 evidence instead of full response).
unfinished_itemsYesQuestion IDs that were not completed in class (e.g., ['SA-1', 'MC-4']). The take-home form will include modified versions of these.
include_parent_noteNoWhether to include a parent/guardian context note explaining the assignment and how to help.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose the substantive behavior of the output (embedded text excerpts, reduced question scope, parent note), which is genuinely useful. But it never states whether anything is persisted, what format the artifact is returned in, or whether the source classwork must already exist, leaving mutation/side-effect questions unanswered.

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?

Front-loaded with the core action, followed by a compact enumeration of output contents and a closing audience qualifier. It is a single dense sentence plus one short clause, with no filler; only the list of artifacts is slightly long relative to the rest.

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?

With only three fully documented parameters and no output schema, the description does the important remaining work: it explains what the generated artifact will contain, which substitutes for a return-value spec. Missing only secondary details such as output format and whether the source classwork record must pre-exist.

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 description coverage is 100%, so all three parameters are already documented, including the default-on reduced_scope and include_parent_note. The description reinforces those concepts ('reduced-scope questions', 'optional parent/guardian note') but adds no format or constraint detail beyond the schema, so baseline 3 applies.

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?

States a specific verb and artifact ('Generate a modified take-home version of classwork the student didn't finish') and then enumerates what the artifact contains (text excerpts, reduced-scope questions, sentence starters, word banks, parent note). This is clearly distinguishable from sibling generators such as generate_lesson_modifications or generate_sub_card.

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 final sentence gives a usage condition — students with low stamina or who shut down during independent practice — which is real when-to-use guidance. However, there is no when-not guidance and no explicit routing against siblings like scaffold_question or generate_lesson_modifications, so the agent must infer the boundary.

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