Skip to main content
Glama
Sign In
unw-mcp

unw-mcp

by HenryGetz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

unw_banner_plan_delete

Deletes an entire Banner plan permanently after requiring a confirm flag and exact plan-name confirmation, preventing accidental removal and returning a before/after diff.

Instructions

Delete an entire Banner plan (writes to Banner, irreversible).

Confirmation is ENFORCED twice: confirm must be true AND confirm_name must equal the plan's exact name. Otherwise the tool reports the intended deletion and current plan state and performs no write. Successful deletion returns the removed plan, remaining plan count and a before/after diff read back from Banner.

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>",
      "plan": "<plan>",
      "confirm": "<confirm>",
      "confirm_name": "<confirm_name>"
    },
    "name": "unw_banner_plan_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
planYes
termYes
confirmYes
confirm_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/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 load and does so well: it declares the write, declares irreversibility, describes the enforced dual confirmation, describes the no-write refusal path and what it reports, and describes the success payload including a read-back diff. It does not cover permissions or rate limits, keeping it short of 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded single-sentence purpose followed by the confirmation mechanics and the two outcome paths. Every sentence adds information an agent needs; nothing is padding.

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?

No output schema exists, and the description correctly specifies the return values on both success and refusal. The main remaining gap is the identity/format of term and plan, which matter for correct invocation of a destructive tool.

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 0%, so the description must compensate for four parameters. It explains confirm (must be true) and confirm_name (must equal the plan's exact name) precisely, but leaves term and the ambiguous plan (string or integer) undefined as to format or accepted identifier form.

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 plus destructive scope: 'Delete an entire Banner plan'. The word 'entire' usefully contrasts with partial removal, though it does not name a sibling alternative explicitly.

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?

Usage is implied by the destructive framing and the double-confirmation precondition, which effectively tells the agent what must be true before calling. However, there is no explicit when-to-use versus alternatives such as the sibling remove/create/add tools, and no guidance on when deletion is inappropriate.

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

Deploy Server

Other Tools