Skip to main content
Glama

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

Расчёт цены

raschet
Read-onlyIdempotent

Точная сумма за товар с выбранными допами и количеством, так же как в корзине сайта, и наличие этого набора (на складе или под заказ со сроком). Без доставки, замера и монтажа (их условия: usloviya). Возвращает ссылку на товар с выбранным вариантом.

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": {
      "id": "<id>",
      "variant_id": "<variant_id>"
    },
    "name": "raschet"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesid товара
dopyNoВыбранные допы: по одному варианту на доп
variant_idYesвариант из tovar
kolichestvoNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare a safe, idempotent, closed-world read, so the bar is low. The description adds genuine context beyond them: the result mirrors the site cart, includes stock-or-made-to-order availability with a timeframe, excludes delivery/measurement/installation, and even states the return value (a product link with the selected variant).

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?

A single front-loaded sentence whose three clauses each carry weight: the computed value, the exclusions with alternative, and the return value. Slightly dense but no filler.

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 read-only calculator with no output schema, the description covers the essentials: what is computed, what is excluded, and what is returned (a link). Availability semantics (in-stock vs made-to-order with lead time) are also disclosed, leaving little an agent must infer.

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 description coverage is 75%, so the schema largely documents the fields itself. The description references selected add-ons and quantity (dopy, kolichestvo) and the returned variant link, but adds little syntax or constraint detail beyond what the schema already provides; baseline 3 applies.

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?

States a specific verb (calculates the exact sum) and resource (product price + availability) with scope, and explicitly carves out what it does not cover. It distinguishes itself from the usloviya sibling by redirecting delivery/measurement/installation conditions there, so an agent can tell it apart without opening the 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?

Gives clear context (replicates the cart calculation) and states when-not to use it by naming the excluded services and the alternative tool (usloviya). It does not, however, explain the ordering relationship with oformit_zakaz or when to prefer it over tovar, so routing to the other siblings is left implicit.

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