Skip to main content
Glama

Remont — renovation planner

Update plan items

update_plan_items

Changes an already shown plan without showing it again: replace a material or tool, set brand/price/link/quantity, add or remove a line, add a stage or items to a stage, rename. The open plan updates itself within seconds; a saved plan (save_plan) is updated too. view_id comes from the show_renovation_plan response.

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": {
      "view_id": "<view_id>",
      "changes": "<changes>"
    },
    "name": "update_plan_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
changesYes
view_idYesview_id from the show_renovation_plan response

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations declare readOnly=false, destructive=false, openWorld=false; the description adds real behavioural context beyond that: the open plan refreshes within seconds and a saved plan is also mutated, so the agent knows the edit has persistent side effects. Minor tension: it advertises remove operations while destructiveHint=false, though plan-line removal is reversible in practice, so this is flagged as a note rather than a contradiction.

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?

Three dense sentences, front-loaded with the key constraint (works on an already shown plan, no re-render), then the effect, then the parameter provenance. No filler or restatement of the tool name.

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 mutation tool with no output schema and only two parameters, the description covers preconditions, supported edit kinds, and the persistence/refresh behaviour. It is silent on what is returned and whether a batch of changes is atomic or partial on failure, which is a real gap for an array-of-edits mutation tool.

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 only 50%, but the description compensates by mapping high-level intents (replace, set, add line, add stage, rename) onto the changes array structure, clarifying that a single call bundles multiple edit kinds and that the view_id is a handle obtained from another tool's response. It does not explain add/remove/key lookup precedence, which the schema also leaves thin.

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?

A specific verb (changes) on a specific resource (already shown plan), followed by an enumerated list of supported edits: replace material/tool, set brand/price/link/quantity, add/remove line, add stage, rename. An agent can distinguish this from show_renovation_plan, save_plan, and open_plan purely from the text.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

The phrase 'an already shown plan without showing it again' plus 'view_id comes from the show_renovation_plan response' establishes the prerequisite and implicitly routes the agent to show_renovation_plan when the plan hasn't been displayed yet. It also notes the interaction with save_plan. It stops short of explicit when-not guidance or naming an alternative for viewing results, so it is strong but not exhaustive.

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