Skip to main content
Glama

Усилитель сигнала

usilitel_request_link

Ссылка на заявку на сайте с уже заполненным подбором. Давайте её, когда человек готов заказать, хочет расчёт, консультацию или монтаж. По ссылке откроется окно заявки: подбор уже в комментарии, человеку останется ввести телефон и отправить — менеджер перезвонит в рабочее время. summary — кратко по-русски: объект, площадь, оператор или частота, что нужно (звонки, интернет), пожелания. НЕ включайте телефон, имя, адрес, почту и другие персональные данные — их человек вводит на сайте сам. product_ids — id или url подобранных товаров (до 10): их названия, цены и наличие добавятся в заявку.

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": {
      "summary": "<summary>"
    },
    "name": "usilitel_request_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
summaryYes
product_idsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it explains what the link does (opens a request window with the selection already in the comment), what the human still must do (enter phone and send), and the callback expectation (manager calls back during business hours). It also states a hard privacy constraint and the up-to-10 product limit with the effect of adding names/prices/availability. Link lifetime or whether the link is single-use is not addressed.

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?

Front-loaded with the purpose, then when to use, then what happens, then per-parameter rules — a logical order. It is somewhat long and the em-dash explanation of the request window could be tightened, but no sentence is filler.

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?

For a two-parameter tool with no annotations and no output schema, everything an agent needs is present: when to call it, what it returns, how to build each argument, and the PII prohibition. Nothing material is left to inference.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must compensate and does: summary is specified by content (object, area, operator or frequency, needed services, wishes), by language (briefly in Russian), and by exclusion (no phone, name, address, email or other PII). product_ids is specified by accepted format (ids or urls), cardinality (up to 10), and downstream effect.

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 names a specific artifact (a link to a site request form with the selection pre-filled) and the action (hand it to the person). It is clearly distinct from siblings like usilitel_equipment_pick or usilitel_products_search, which pick/search rather than produce an order link.

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?

Trigger conditions are explicit: hand it over when the person is ready to order, wants a calculation, a consultation, or installation. No sibling is named as an alternative and no when-not condition is given, so it falls 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.