Skip to main content
Glama

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

usilitel_refresh

Немедленно сверить данные с сайтом, не дожидаясь планового обновления (оно идёт само каждые несколько минут). Вызывайте, только если пользователь прямо просит обновить данные.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/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. It usefully discloses that a background refresh already exists on a few-minute cadence, which tells the agent this call is a forced override rather than the normal path. It says nothing about how long the sync takes, whether it can fail or be rate-limited, or what the caller observes afterwards — meaningful gaps for a mutation-like trigger.

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 short sentences, zero waste, and the constraint ('only if the user asks') is front-loaded after the action statement. Nothing is repeated from the schema because there is nothing to repeat.

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

Completeness4/5

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

For a no-parameter, no-output-schema trigger tool this covers the essentials: what it does, why it is usually unnecessary, and when it is permitted. The remaining omission — duration or side effects of the forced refresh — is minor given the tool's simplicity.

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 there is no schema semantics to add and the baseline is 4. The description correctly implies a no-argument trigger by describing the action purely in terms of timing.

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 verb and resource: immediately re-sync data with the site rather than waiting for the scheduled refresh. That is clear enough to distinguish it from the read-only siblings (catalog, products, articles), none of which force a sync. It stops short of naming any sibling explicitly, so a 5 is not warranted.

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?

It gives an explicit gating condition: call only when the user directly asks to refresh data. It also implicitly names the alternative path — the automatic refresh that runs every few minutes — so an agent knows the default is to do nothing. It does not discuss other situations (e.g. staleness suspected but not requested), but the core when/when-not is present.

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.