Skip to main content
Glama

Remont — renovation planner

Data coverage report

get_coverage
Read-only

Data coverage report for countries: which reference prices, real labor rates, catalog products (with links) and store prices exist in the database, what is missing or stale. Use it to decide what to look up and save (save_catalog_items, save_prices, save_labor_rates) — e.g. when asked to fill the database for a country. Without country — a short summary for all countries.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_coverage"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryNoISO country code; omit for all countries

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 establish that this is a read-only, closed-world operation, so the description does not need to re-litigate safety. It adds genuine behavioral context beyond that: the report distinguishes existing data from missing or stale data, includes links for catalog products, and degrades to a short summary across all countries when no country is given.

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 purpose and the payload enumeration are front-loaded in the first sentence, and the no-country fallback is placed last where it belongs. The em-dash aside listing three save tools is slightly run-on, but every clause carries information an agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description carries the burden of describing returns and it does so by naming the four data categories plus the missing/stale dimension. With one optional parameter and full schema coverage, nothing an agent needs in order to call this correctly is absent.

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 100% and the single parameter is already documented as an ISO country code with 'omit for all countries'. The description still adds meaning by clarifying that omitting the country produces a *short summary* rather than a full detailed report, which is a behavioral difference the schema does not convey.

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 resource (data coverage report) and enumerates exactly what it reports on: reference prices, real labor rates, catalog products with links, store prices, plus what is missing or stale. That level of enumeration lets an agent distinguish it from read-oriented siblings like get_catalog or get_country_profile without opening a 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 states the decision it supports ('use it to decide what to look up and save') and names the three write tools that follow it (save_catalog_items, save_prices, save_labor_rates), with a concrete trigger ('when asked to fill the database for a country'). There is no explicit when-not-to-use condition, so it falls just short of a 5.

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