Skip to main content
Glama

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

usilitel_catalog_status

Свежесть и объём данных: когда сайт последний раз пересобирался, когда сервер сверялся с сайтом, сколько товаров (и в наличии), страниц, статей и PDF-документов. Вызывайте, если спрашивают, насколько актуальны данные.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

No annotations are supplied, so the description carries the burden — and it does disclose what the call reports (read-only status snapshot of rebuild/sync timestamps and record counts). It does not mention staleness thresholds, caching, or refresh side effects, but there is little behavioral risk in a no-argument status read.

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?

Two sentences, front-loaded with what the status contains and followed by the invocation trigger. The enumeration is long but each item earns its place because no output schema exists to carry it.

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?

With no output schema and no parameters, the description must substitute for the return-value documentation, and it does so by listing exactly which freshness and volume figures come back. Nothing an agent needs in order to call it correctly is missing.

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 there is nothing for the description to clarify beyond the schema; baseline 4 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 resource and scope: data freshness and volume — last site rebuild time, last server-to-site sync, counts of products (and in-stock), pages, articles and PDFs. The enumerated contents make it clearly distinct from siblings like usilitel_refresh (which presumably triggers an update) and usilitel_catalog_changes.

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 an explicit trigger: call it when the user asks how current/up-to-date the data is. It does not name an alternative tool or a when-not condition, but for a zero-parameter status probe the positive trigger is the decisive guidance an agent needs.

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.