Skip to main content
Glama

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

usilitel_content_search

Поиск по статьям блога и текстам разделов, подборок и услуг (не по товарам — для них usilitel_products_search). Возвращает подходящие страницы с фрагментом текста.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "usilitel_content_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose the return shape ('matching pages with a text snippet'), which is valuable since there is no output schema, but it says nothing about result ranking, pagination beyond the limit default, or whether the corpus spans all site languages.

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 filler, with the search scope leading and the product exclusion following immediately. Nothing is redundant and nothing is buried.

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 two-parameter search tool this covers the essentials of what it searches and roughly what it returns. However, with 0% schema coverage and no output schema, the omission of query matching behavior and limit semantics leaves an agent guessing on invocation details.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate and it does not — neither 'query' (matching semantics, language, phrase vs keyword) nor 'limit' (default 10, max?) receives any explanation. Only the broad notion of searching is implied by the description, leaving both parameters to be guessed.

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 verb+resource: search across blog articles and section/collection/service texts, and explicitly carves out what it does NOT cover (products) while naming the sibling usilitel_products_search. An agent can distinguish it from usilitel_products_search without opening either schema.

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 exclusion plus the correct alternative for product lookups, which is real routing guidance. It stops short of distinguishing this from other content-adjacent siblings such as usilitel_page_text or usilitel_articles, so the when-to-use side of the picture is only partly drawn.

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.