Skip to main content
Glama

Remont — renovation planner

Save plan

save_plan

Saves the plan on the server, only if the user asked to save it. Without user_code it creates a new personal code and returns it — show the code to the user and ask them to write it down: with it they can open their plans in any chat. Nobody else needs the code and it cannot be recovered.

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": {
      "plan": "<plan>"
    },
    "name": "save_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
planYesThe same object you pass to show_renovation_plan (title, locale, currency, mode, stages, materials, notes…)
plan_idNoIf you are updating an already saved plan
view_idNoview_id of the shown plan — then line edits and checklist ticks are saved too, and the open plan remembers the code
user_codeNoUser's personal code if they already have one, e.g. oak-river-moon-4821

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already establish this is a non-destructive write with no open-world access, and the description adds meaningful behavior beyond that: absence of user_code creates a new personal code that is returned, the code is private, and it cannot be recovered. The irreversibility/privacy disclosure is exactly the kind of context annotations cannot convey, though it stops short of describing failure modes or what a save returns otherwise.

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?

Three sentences, front-loaded with the action and its precondition before the code-handling branch. Nearly every clause carries operational weight; the closing sentence about secrecy and non-recovery is slightly padded but still justifies itself as user-facing instruction.

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?

There is no output schema, and the description compensates by stating what is returned when a code is created and what the agent should do with it. For a nested-object write tool with full schema coverage, this is close to complete; only error or conflict behavior is left unstated.

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 100%, setting a baseline of 3, and the description adds real meaning on top: it explains the consequence of omitting user_code (a new code is generated and must be shown to the user) and reinforces the plan_id/view_id update paths. The added value is concentrated on user_code, with the other parameters left to the schema.

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?

The description uses a specific verb and resource ('Saves the plan on the server') and immediately scopes it with a conditional ('only if the user asked to save it'). It is clearly distinguishable from siblings such as save_progress, save_view_progress, or save_layout because it names the plan object and the personal-code mechanism.

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?

It gives an explicit precondition for invocation ('only if the user asked to save it') and describes the branch when no user_code is supplied, which is the main decision an agent faces. It does not explicitly contrast with open_plan or update_plan_items, so a small inference gap remains.

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