Skip to main content
Glama

Remont — renovation planner

Save plan progress

save_progress

Saves ticked tasks of the plan. Called by the plan widget.

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>",
      "checks": "<checks>"
    },
    "name": "save_progress"
  }
}

Input Schema

NameRequiredDescriptionDefault
whoNo
haveNo
tiersNo
boughtNo
checksYes
plan_idYes
user_codeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already establish write, non-destructive, closed-world, and the description is consistent with them. Beyond that it adds nothing: no statement of whether existing checks are replaced or merged, whether partial payloads are allowed, or what happens to the unrelated who/have/tiers/bought data on save.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

Two very short sentences with the action front-loaded and no filler. The second sentence is meta-information about the calling widget that occupies half the text without informing tool selection.

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?

A mutation tool with 7 undocumented parameters, nested objects, and no output schema needs much more than two sentences. An agent could not determine what the have/bought/tiers maps are for or how the save behaves on conflict from this definition.

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?

With 0% schema coverage across 7 parameters and nested objects, the description carries the full semantic burden, yet it only gestures at 'checks' via "ticked tasks." The six other parameters (user_code, plan_id, who, have, tiers, bought) and the meaning of their key-value maps are entirely unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Saves ticked tasks of the plan" gives a verb and a rough resource, so the agent knows this persists checkbox state. But it never distinguishes itself from close siblings such as save_view_progress, save_plan, or mark_bought, and "ticked tasks" is not mapped to any named field.

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

Usage Guidelines2/5

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

"Called by the plan widget" describes the caller, not the condition for choosing this tool. There is no when-to-use, no exclusion, and no pointer to save_view_progress or save_plan as alternatives for other kinds of progress.

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