Skip to main content
Glama

Remont — renovation planner

Save user preferences

save_preferences

Saves the user's preferences under their personal code so they are selected by default in every new plan: tools they own and preferred non-consumable products (e.g. a tile brand, a specific boiler, a tap). Call when the user says what they own or which product they always want. Ticking 'have' and choosing an option in a saved plan updates preferences automatically. With no changes it just returns the current preferences.

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

Input Schema

NameRequiredDescriptionDefault
forgetNoMaterial keys to forget
materialsNoPreferred product per material key (non-consumables), e.g. {"floor_tiles": {name, price, store, url, country}}
user_codeYesPersonal code
tools_haveNoTool names the user owns (add)
tools_removeNoTool names to remove from owned

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the annotations, the description explains persistence across new plans, automatic updates through saved-plan interactions, and the no-change behavior of returning current preferences. It does not explain merge/replace semantics for materials or the consequences of forget/tools_remove, but it adds meaningful behavioral context for a mutation tool.

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?

The description is front-loaded with the core purpose and uses short, mostly information-bearing sentences. The examples and automatic-update note are useful context, though the passage is slightly longer than strictly necessary.

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 preference-mutation tool with a nested materials object and no output schema, the description covers the key intent, defaulting behavior, automatic update path, and no-change return behavior. Remaining gaps around removal semantics and precise return format are minor relative to the schema and annotations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the input schema already documents all five parameters in detail. The description adds useful framing by identifying personal code, owned tools, and preferred non-consumable products, but it does not add semantics for forget or tools_remove beyond what the schema already provides.

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 gives a specific verb and resource: saving the user's preferences under their personal code so they become defaults in new plans. It also specifies the preference content types, owned tools and preferred non-consumable products, which distinguishes this from generic plan/catalog save siblings.

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 clearly says to call when the user states what they own or which product they always want. It also explains that preference updates happen automatically when users tick 'have' or choose an option in a saved plan, and that no changes simply returns current preferences. It lacks an explicit named alternative tool, but the usage context is clear.

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