Skip to main content
Glama

unw_banner_plan_create

Create a named Banner Plan Ahead worksheet for a term with required confirmation before writing, so users can verify the intended effect and avoid unconfirmed changes.

Instructions

Create a named Banner Plan Ahead worksheet for term (writes to Banner).

Confirmation is ENFORCED, not advisory: confirm is required and must be true, otherwise the tool returns the intended effect and the current plan count without writing. Verify the effect with the user first. The student may hold at most five plans per term; names cannot be renamed later.

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": {
      "term": "<term>",
      "name": "<name>",
      "confirm": "<confirm>"
    },
    "name": "unw_banner_plan_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
termYes
confirmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior5/5

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

With no annotations present, the description carries the full burden and does so well: it discloses the write target (Banner), that confirmation is ENFORCED rather than advisory, exactly what happens on a false confirm (returns intended effect plus current plan count with no write), the five-plans-per-term quota, and that names are immutable after creation.

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 side effect and resource identity are front-loaded in the first sentence, followed immediately by the highest-risk behavioral detail (enforced confirmation). Every sentence adds a distinct constraint; no filler.

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 three-parameter mutation tool with no annotations and no output schema, it covers the critical unknowns: write behavior, confirmation semantics, quota, and immutability. What is missing is term format and any name length/character constraints, plus what a created plan contains.

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 0%, so the description must compensate, and it covers all three parameters: it explains confirm's enforcement semantics and non-confirmation return path, and notes that name cannot be changed later. It leaves term's expected format (code vs. label) unspecified, so not fully compensating.

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?

States a specific verb and resource ('Create a named Banner Plan Ahead worksheet for term') and flags the side effect ('writes to Banner'). It does not explicitly contrast itself with the similarly named sibling unw_banner_plan_add, so an agent must infer the distinction, which keeps it below 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 Guidelines3/5

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

Gives clear procedural guidance for this tool ('Verify the effect with the user first', confirmation is required), which is real usage context. However, it never says when to prefer this over unw_banner_plan_add or unw_plan_draft, so alternative selection is left to inference.

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