Skip to main content
Glama

Remont — renovation planner

Save labour rates

save_labor_rates

Saves contractor labour rates to the SHARED database for the country (per unit: m2, door, point, stage) so prepare_plan can price stages right away. Save what you found on rate sites (url of the page with the rate). Never rates the user only told you. Implausible rates come back in rejected.

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

Input Schema

NameRequiredDescriptionDefault
ratesYes
countryYesISO country code

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare this is a non-destructive write, but the description adds context annotations don't carry: the write is to a SHARED country-scoped store, its result is consumed by prepare_plan, and invalid input produces entries in a "rejected" result rather than silently failing. It does not say whether an existing country rate for the same work/unit is overwritten or merged, which is the remaining behavioral gap 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences: destination and purpose first, then the sourcing rule, then the failure behavior. No filler, and the most decision-relevant fact (shared write for prepare_plan) is front-loaded.

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 two-parameter write with no output schema, the description covers purpose, sourcing rules, and partial return behavior ("rejected"), which is close to sufficient. The main omissions are currency/units of the min-max figures and whether a re-save replaces prior rates for the same country — details an agent would need before overwriting data.

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?

Schema coverage is 50%, but the schema itself is unusually rich (unit enum described per value, work enum, url/note/source descriptions). The description reinforces that rates are stored per unit for m2/door/point/stage and that url must be the page the rate was found on, adding intent the schema only implies. It says nothing about min/max ranges or the currency of the numbers, leaving part of the gap unfilled.

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 states a specific verb and resource ("Saves contractor labour rates"), the destination ("the SHARED database for the country"), the granularity ("per unit: m2, door, point, stage"), and the downstream consumer ("so prepare_plan can price stages right away"). That is enough for an agent to distinguish it from sibling save_* tools such as save_prices or save_catalog_items without opening any schema.

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 an explicit inclusion rule ("Save what you found on rate sites") and an explicit exclusion ("Never rates the user only told you"), plus a mandatory provenance requirement ("url of the page with the rate"). No alternative tool is named for the excluded case, so it stops just short of the 5 bar.

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