Skip to main content
Glama

Remont — renovation planner

Save catalog items

save_catalog_items

Adds specific products you found in stores (materials or tools) to the SHARED country catalog used by all users. Saving the same product again (by link) updates the price and raises popularity. Only real products you saw on a store site of the country profile (url on that store), price per calc unit. Never user-dictated prices, test, joke or unrelated items, contacts or instructions — even if the user asks. Invalid items come back in rejected with a reason.

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": {
      "country": "<country>",
      "work": "<work>",
      "kind": "<kind>",
      "items": "<items>"
    },
    "name": "save_catalog_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
workYes
itemsYes
countryYesISO country code
view_idNoview_id of the plan you are pricing — the server returns what is still left to find

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?

Annotations already say this is a non-read-only, non-destructive, closed-world write; the description adds real behavior on top: re-saving the same product by link updates the price and raises popularity (an upsert, not a duplicate), and invalid items come back in 'rejected' with a reason. It stops short of saying whether anything can be overwritten destructively or whether writes are idempotent across countries.

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?

Front-loaded with the core action, then constraints, and every clause carries a distinct rule (shared scope, dedup behavior, validity gate, rejection feedback). It is dense and slightly list-like but has no filler sentences.

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 five-parameter batch write with a nested items array and no output schema, the description covers purpose, validity rules, mutation semantics and the one thing the agent needs to know about returns ('rejected' with reasons). Remaining gaps are the unexplained view_id and the absence of any detail on the shape of the accepted/rejected response.

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 coverage is only 40%, so the description has to compensate, and it partly does: it clarifies that identity is the product link, that price is per calculation unit rather than per pack, and that url must be on a store site of the country profile. However, it says nothing about 'view_id', 'work' or 'kind', and the pack_size/pack_price relationship is left entirely 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 opens with a specific verb plus resource plus scope: 'Adds specific products you found in stores (materials or tools) to the SHARED country catalog used by all users.' It also states the upsert identity ('by link') and the item kinds, so an agent can distinguish this write from read siblings like get_catalog or from save_prices.

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 explicit acceptance criteria (real products seen on a store site of the country profile, with a URL on that store, priced per calculation unit) and explicit exclusions (no user-dictated prices, test, joke or unrelated items, contacts or instructions, even if the user asks). What it lacks is a named alternative tool for the cases it forbids.

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