Skip to main content
Glama

Remont — renovation planner

Save country profile

save_country_profile

Adds a country or extends a SHARED profile: stores, rate sites, rules. Stores are merged with existing ones by domain. Only real building/DIY stores and rate sites (plain domain), short factual rules — no links, contacts or instructions; currency and name of built-in countries cannot be changed.

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": {
      "code": "<code>"
    },
    "name": "save_country_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesISO country code
nameNo
notesNo
localeNoSearch language in stores
storesNoDIY/building stores with prices on their site
currencyNoISO currency code
laborSourcesNoSites with contractor rates
specialistRulesNo

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?

Beyond readOnlyHint=false/destructiveHint=false, the description discloses real behavior: stores are MERGED by domain rather than replaced, and built-in countries' currency and name are immutable. It also states the write invalidates low-quality content (no links, contacts or instructions). The gap is that merge vs. overwrite semantics are only specified for stores, not for notes/specialistRules/laborSources.

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?

Two dense sentences with the primary purpose front-loaded and constraints packed into the second; nothing is redundant. The semicolon-chained constraint clause is slightly run-on but still scannable.

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 write tool with no output schema and 8 parameters at 63% coverage, the description supplies the merge rule and the immutability constraints that an agent most needs before mutating shared data. It could say whether omitted fields are preserved, but otherwise it is sufficient to call the tool correctly.

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

Parameters4/5

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

With 63% schema coverage, the description carries useful extra meaning: it clarifies that stores must have a plain domain, that 'rate sites' correspond to the laborSources parameter, and that specialistRules should be short factual statements. It leaves code, locale and notes unexplained, but adds genuine semantics over the schema for the highest-risk parameters.

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?

The description names a specific verb and resource ('Adds a country or extends a SHARED profile') and enumerates the payload it carries (stores, rate sites, rules), which is more precise than the name alone. It implicitly contrasts with the read-side sibling get_country_profile via 'extends a SHARED profile', but never names it explicitly, so it stops short of full sibling differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the two use cases — adding a new country versus extending an existing shared profile — which tells the agent when the tool applies. However, no alternative is named and no when-not condition is given; an agent is left to infer that read/query work belongs to get_country_profile.

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