Skip to main content
Glama

Между Комнат: двери в Москве

Карточка товара

tovar
Read-onlyIdempotent

Всё о товаре: описание, характеристики, варианты (цвет, комплектность) с ценой и наличием, допы (размер полотна, открывание, стекло, наличники, врезка) с ценами для выбранного варианта. Поле komplektnost: что входит в цену (комплект с коробкой и наличниками или только полотно) и погонаж к двери.

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": "tovar"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoid товара из poisk
urlNoили адрес страницы товара на me-ko.ru
variant_idNoвариант, для которого показать цены допов (по умолчанию основной)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds content-level transparency by explaining what the komplektnost field means and that extras prices are computed for the selected variant. It does not describe pagination, failure modes, or whether a missing/ambiguous id and url is tolerated.

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, front-loaded with the resource identity, then the returned field groups and the komplektnost semantics. Dense but every clause carries content; only the long parenthetical enumerations of extras slightly tax readability.

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 usefully carries the return-value burden by naming the field groups and explaining komplektnost. A read-only, three-optional-parameter tool needs little more, though it could state whether id or url is preferred when both are supplied.

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 100% and no parameters are required, so the baseline is 3. The description adds marginal value by tying the extras pricing to 'выбранного варианта' (variant_id) and clarifying that komplektnost describes what is included in the price, but it adds no format or precedence detail beyond the schema's own id/url/variant_id notes.

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 the resource clearly ('Карточка товара') and enumerates what it returns: description, characteristics, variants with price/availability, and extras with per-variant pricing. The retrieval intent is unambiguous, though it never contrasts itself with siblings like poisk or oformit_zakaz, so an agent must infer the boundary itself.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance appears in the description. It never mentions that poisk supplies the id, nor how it differs from raschet or oformit_zakaz; the only routing hint lives in the schema ('id товара из poisk'), which is structured data, not description guidance.

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