Skip to main content
Glama

Remont — renovation planner

Save prices

save_prices

Saves prices found in stores to the SHARED price cache (used by all users). Only prices you saw on a store site of the country profile, with the product url; price per material unit from calculate_materials, in the country's currency. Never prices the user only told you. 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>",
      "prices": "<prices>"
    },
    "name": "save_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNo
pricesYes
countryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations say readOnly=false and destructive=false but reveal nothing about scope or validation. The description adds two behaviors beyond them: writes go to a cache shared by all users (so entries affect others), and invalid entries are returned in `rejected` with a reason rather than silently failing. Permission requirements and overwrite behavior for existing keys are not stated.

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 shared-cache warning and the sourcing constraint are front-loaded, and the rejection behavior is stated compactly at the end. The middle clause is a dense run-on semicolon chain, but no sentence is filler.

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 mutation that writes to global shared state with no output schema and three parameters at 0% description coverage, the description covers preconditions well but leaves the nested price object and the returned `rejected` payload shape underspecified. An agent could still call it, but might produce rejected items on the first attempt.

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 0%, so the description must carry the meaning and it partly does: it constrains the price value (per material unit from calculate_materials, country currency) and requires the product url. It leaves `city`, `key`, `ean`, and the `source.type` variants (store_page|flyer|search|user|other) unexplained, and never says what distinguishes `country` from `city`.

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 concrete verb+resource: saving store prices into a SHARED price cache used by all users, which makes the side effect on other users explicit. It is distinguishable from the read-side sibling (find_cached_prices) by the "Saves ... to the cache" framing, though it never names an alternative tool directly.

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?

Gives clear inclusion criteria (prices you saw on a store site of the country profile, with the product url, per material unit from calculate_materials, in the country's currency) and an explicit exclusion ("Never prices the user only told you"). What is missing is an explicit pointer to which sibling to use instead when the exclusion applies.

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