Skip to main content
Glama

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

usilitel_page_text

Текст страницы сайта: раздела, подборки («/repiteri/dlya-dachi/»), бренда, услуги или главной — заголовок, описание, текст блоками и вопросы-ответы. Используйте для объяснений «как выбрать», условий услуг.

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": {
      "path_or_url": "<path_or_url>"
    },
    "name": "usilitel_page_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
path_or_urlYes

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 exist, so the description carries the full behavioral burden. It usefully discloses the shape of the returned content (heading, description, block text, Q&A), but says nothing about whether the fetch is live or cached, how invalid paths or missing pages behave, or size/pagination limits.

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 sentences, front-loaded with the resource, then the payload list, then the usage cue. Dense but every clause adds information; the parenthetical example earns its place by showing the path format.

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 one-parameter read tool with no output schema, the description does the important work of describing what comes back, which is the main gap it needs to fill. It remains incomplete on parameter format rules and failure behavior, leaving the agent to guess before calling.

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 coverage is 0%, so the single parameter 'path_or_url' is documented nowhere except the name. The description partially compensates by giving a concrete path example ('/repiteri/dlya-dachi/'), implying relative paths are accepted, but it never states whether absolute URLs work or what format errors look like.

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 ('Текст страницы сайта') and enumerates what it covers: section, collection, brand, service, or main page, plus the returned content (заголовок, описание, текст блоками, вопросы-ответы). It implies a distinction from sibling article/list tools only indirectly via the 'page' framing, so it stops short of a 5.

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?

Gives a positive when-to-use cue ('для объяснений «как выбрать», условий услуг'), which helps an agent pick this over usilitel_articles or usilitel_article. It offers no exclusions, no explicit alternative routing, and no prerequisites, so the guidance is implied rather than decisive.

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.