Skip to main content
Glama

Remont — renovation planner

Save furniture

save_layout_furniture

Internal: the plan widget saves furniture moved by the user. 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>",
      "floor": "<floor>",
      "furniture": "<furniture>"
    },
    "name": "save_layout_furniture"
  }
}

Input Schema

NameRequiredDescriptionDefault
revNo
doorsNo
floorYes
presetsNo
view_idYes
furnitureYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the safety profile is covered structurally. The description adds genuinely useful context that the tool is invoked automatically by an internal widget, but says nothing about what existing data is overwritten or what permissions are required for the write.

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 front-loaded and the 'do not call' directive immediately after. Nothing is wasted and the agent can act on it in one read.

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 instructed not to invoke, the description covers the essential decision (skip it), which is why it is not inadequate. However, six undocumented parameters and no statement of what the write persists or returns leave gaps if an agent ever had reason to call it.

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% across six parameters, so the description carries the full burden and largely fails. Only 'furniture' is loosely gestured at ('furniture moved by the user'); view_id, floor, rev, doors and presets get no explanation of format, requiredness or effect.

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?

States a specific verb and resource ('saves furniture moved by the user') and identifies the caller (the plan widget), which distinguishes it from the many sibling save_* tools. It stops short of saying what a 'save' persists or replaces, so it is clear but not fully specified.

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?

Explicitly tells the agent 'You do not need to call it', which is a direct when-not-to-use instruction — rare and valuable. It does not name an alternative tool for cases where the agent does need to persist layout data, leaving that inference to the sibling list.

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