Skip to main content
Glama

Remont — renovation planner

Get catalog

get_catalog
Read-only

Popular materials and tools by work type for the country: the base list and specific products (brand, tier, price, link) that were already found and saved. Sorted by popularity. Use before searching prices and when the user asks to replace a material or tool.

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

Input Schema

NameRequiredDescriptionDefault
keyNoMaterial key (e.g. floor_tiles) or tool name — only options for it
kindNoOnly materials or only tools
tierNo
workNoWork type; without it — all
countryYesISO country code
ui_localeNoLanguage of the user's messages (not of the country), any code: en, ru, pl, uk, de, fr, es… Always pass it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare this is a read-only, closed-world operation, so safety needs no further explanation. The description does add genuine behavioral context that annotations cannot: the result mixes a base list with previously saved/found products and is ordered by popularity. It says nothing about result size, paging, or what happens when no saved products exist for the country.

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 sentences: the first front-loads the returned resource and shape, the second front-loads when to call it. There is no filler. The parenthetical field list is slightly dense but earns its place by defining the payload.

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?

With no output schema, the description must describe the payload, and it does (base list plus saved products with brand, tier, price, link, popularity-sorted). Six parameters at high schema coverage are handled by the schema, and read-only semantics are handled by annotations. The only material gap is absence of any note on result volume or empty-state behavior.

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 83%, so the schema already documents key, kind, tier, work, country and the ui_locale instruction to always pass it. The description reinforces the work-type scoping and country dimension but adds no new semantics for key, kind, tier, or ui_locale. Baseline 3 is appropriate when the schema carries the parameter burden.

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 concrete resource (catalog of popular materials and tools) and enumerates the returned product fields (brand, tier, price, link) plus the ordering rule (sorted by popularity), so an agent knows exactly what it gets. It stops short of naming a sibling tool outright, referring only obliquely to 'searching prices', so differentiation is implied rather than explicit.

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?

Two clear activation conditions are given: 'Use before searching prices' and 'when the user asks to replace a material or tool'. That is real sequencing guidance relative to a price-search flow. It does not state when *not* to use it or name the alternative tool directly, which keeps it out of the top band.

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