Skip to main content
Glama

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

usilitel_catalog_changes

Что изменилось на сайте за последние дни (с момента, как сервер следит за сайтом): новые и ушедшие товары, изменения цен и наличия, обновлённые карточки (характеристики, PDF, текст), новые статьи, обновлённые тексты страниц. kind — new_product | removed_product | price_changed | stock_changed | card_updated | new_article | new_page | page_text_updated.

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

Input Schema

NameRequiredDescriptionDefault
daysNo
kindNo

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?

No annotations are supplied, so the description carries the full burden. It discloses the important behavioral trait that results are bounded by when server-side tracking started, but says nothing about ordering, result size, pagination, or what an empty result means for a potentially large change feed.

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 compact sentences, front-loaded with the resource and scope, followed by a token mapping. The change categories are enumerated twice (prose then kind tokens), which is mild redundancy but the second list adds the exact accepted values.

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?

With no output schema and no annotations, the description should say more about the shape of the response (grouped by kind? chronological? empty-feed behavior). For a two-parameter read tool it is adequate, but an agent cannot predict the response structure before calling it.

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 0%, and only the 'kind' parameter gets real treatment: the description supplies the full token vocabulary (new_product, removed_product, price_changed, ...), which the schema does not encode as an enum. The 'days' parameter is only obliquely referenced by 'за последние дни' — its default of 7, allowed range, and interaction with the tracking start date are unstated.

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 a specific verb+resource: a change feed of what changed on the site since tracking began, then enumerates the change categories (products, prices, stock, cards, articles, page texts). That is enough to distinguish it from siblings like usilitel_catalog_status or usilitel_refresh, though it never names an alternative explicitly.

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?

The phrase 'с момента, как сервер следит за сайтом' clarifies the time basis of the feed, which is genuine usage context. However there is no explicit when-to-use guidance, no exclusions, and no pointer to the sibling tools (catalog_status, content_search, refresh) that an agent should consider instead.

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.