Skip to main content
Glama

Remont — renovation planner

Delete plan

delete_plan
Destructive

Deletes a saved plan. Only on the user's explicit request and after confirmation.

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": {
      "user_code": "<user_code>",
      "plan_id": "<plan_id>"
    },
    "name": "delete_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
plan_idYes
user_codeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description adds real behavioral context beyond that by imposing a confirmation requirement, but it omits what actually gets destroyed (plan contents, associated items, shared access) and whether the deletion is recoverable.

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?

Two short sentences, with the action front-loaded and the guardrail following. Nothing is wasted, though the second sentence is abstract enough that it could be tightened with a concrete condition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a destructive, irreversible-in-appearance operation with zero parameter documentation and no output schema. The definition should clarify the blast radius of deletion and the identifier requirements; as written, an agent can call it but cannot confidently predict the outcome.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and both required parameters (user_code, plan_id) are undefined in the schema. The description compensates with nothing — it never explains what plan_id refers to or the role of user_code, leaving the agent to infer the identifier contract.

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 uses a specific verb and resource ("Deletes a saved plan"), which an agent can immediately distinguish from siblings like get_plan, list_plans, or save_plan. It stops short of naming a sibling explicitly, but the resource qualifier "saved" does the disambiguation work.

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?

It provides a clear gating condition — use only on explicit user request and after confirmation — which is genuine when-to-use guidance. However, it offers no routing relative to alternatives (e.g., removing items via update_plan_items instead of deleting the whole plan) and does not define what "confirmation" means in practice.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources