Skip to main content
Glama

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

usilitel_catalog_sections

Структура каталога: разделы с числом товаров (и в наличии), подборки внутри разделов (по объекту, частоте, оператору, бренду, типу), бренды и страницы услуг — с адресами на сайте.

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_catalog_sections"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/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 behavioral burden, and it does describe the returned payload in useful detail (counts, in-stock counts, collection dimensions, URLs). However, it never states that the call is read-only and side-effect free, nor whether the data is cached/stale or requires usilitel_refresh to update. The 'числом товаров (и в наличии)' phrasing hints at aggregate counts but not how current they are.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense sentence that front-loads the resource ('Структура каталога') and then packs the payload dimensions into a parenthetical enumeration. No filler, no repetition, and the trailing 'с адресами на сайте' is a genuinely useful fact rather than padding.

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?

The tool is simple (no parameters, no output schema), so the description must explain what comes back, and it roughly does. But without annotations or an output schema, an agent still cannot tell the response shape (nested tree? flat list?), freshness guarantees, or scope (whole catalog vs. a site/branch). Given the presence of usilitel_refresh and usilitel_catalog_changes among the siblings, a sentence on staleness and scope would have closed the gap.

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 zero parameters, so the baseline is 4 and there is nothing for the description to disambiguate. No misleading parameter hints are present either.

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 states a specific resource (catalog structure) and enumerates its parts precisely: sections with product counts and in-stock counts, curated collections broken down by object/frequency/operator/brand/type, brands, and service pages, all with site URLs. An agent can tell it is a catalog-taxonomy listing rather than a product search. It does not differentiate itself from siblings such as usilitel_catalog_status, usilitel_catalog_changes, or usilitel_products_search, and it never uses an explicit verb.

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?

There is no when-to-use statement, no exclusions, and no mention of alternatives, despite 13 sibling tools including several catalog-related ones (catalog_status, catalog_changes) and product lookups. Use for catalog browsing is only faintly inferable from what the payload contains. An agent has to guess whether this is a snapshot, a navigation map, or a live inventory view.

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.