Skip to main content
Glama

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

usilitel_contacts

Контакты и условия магазина: телефон, почта, часы работы, регион, бесплатный подбор и замер, монтаж, как заказать, доставка (сроки и стоимость), оплата, возврат.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the content domains the call will surface. However, it says nothing about the return shape (raw page text vs structured fields), whether the data is static or live, or the output language, which matters for a zero-parameter fetch tool.

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 with the core framing ('contacts and shop terms') first and the covered topics after. The keyword enumeration is dense but each item maps to a real user question, so little is wasted.

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

Completeness3/5

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

For a trivial no-argument read tool with no output schema, the description covers the topic scope adequately. It is still ambiguous about what is actually returned and how it differs from usilitel_page_text or usilitel_content_search, which an agent needs in order to choose correctly.

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?

The tool takes no parameters, so the baseline is 4 and there is no argument meaning to explain. The description appropriately spends its words on coverage rather than nonexistent inputs.

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 the resource (store contacts and shop terms) and enumerates the exact topics covered — phone, email, hours, region, delivery, payment, returns — which distinguishes it from the product/catalog siblings. It lacks an explicit verb ('returns', 'fetches'), so the verb is inferred rather than stated, keeping it below 5.

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

Usage Guidelines3/5

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

Usage is only implied through the topic list: an agent can infer it should call this for delivery, payment, or contact questions. There is no explicit when-to-use statement, no exclusions, and no routing away from the overlapping sibling usilitel_page_text.

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.