Skip to main content
Glama

Remont — renovation planner

Save checklist progress

save_view_progress

Internal: the open plan saves checklist ticks and switches. You do not need to call it.

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

Input Schema

NameRequiredDescriptionDefault
whoNo
haveNo
tiersNo
tmodeNo
boughtNo
checksNo
choiceNo
view_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

The description adds real context beyond the annotations by declaring that saving happens automatically when the plan is open, which explains why a mutating (readOnlyHint=false) tool requires no call. With annotations already marking it non-destructive and closed-world, the remaining gaps are what an actual call would do to existing state and whether any return value is produced.

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?

Two short sentences, with the internal/automatic nature and the do-not-call instruction front-loaded. Nothing is wasted or buried.

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

Completeness3/5

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

For a tool the agent is told not to invoke, the essential message is delivered. However, with eight undocumented parameters, a nested-object payload, and no output schema, an agent that ever must call it is left with no usable information about what to send.

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 six of the eight parameters (who, have, tiers, tmode, bought, checks, choice) are opaque nested objects with no documentation anywhere. The description offers no explanation of view_id or any of these objects, so it fails to compensate for the coverage gap.

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 checklist ticks and switches" gives a verb and a resource, and the "Internal" marker frames it as a system-managed operation rather than an agent-facing one. But it is broadly scoped to the open plan and does not distinguish itself clearly from near-duplicate siblings such as save_progress or save_plan.

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 definition contains an explicit exclusion: "You do not need to call it," which is exactly the guidance that prevents an agent from invoking it at all. It falls short of a 5 because it names no alternatives and gives no condition under which the agent genuinely might call it.

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