Skip to main content
Glama

КМВ INFO — новости Кавминвод

Поиск по архиву

search_news
Read-onlyIdempotent

Поиск новостей по словам (в заголовке, анонсе и тексте) и датам. Архив — с марта 2026 года.

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": "search_news"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoГород или регион: «Пятигорск», «pyatigorsk», «КМВ», «Ставрополье»; «Россия», «Мир», «Кавказ» — новости вне края. Пусто — Кавминводы и край.
limitNo
queryYesСлова для поиска, например «отключение воды Ессентуки»
date_toNoПо дату включительно, ГГГГ-ММ-ДД
date_fromNoС даты, ГГГГ-ММ-ДД

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: which fields are matched (headline, teaser, body) and the temporal boundary of the corpus. It still omits result ordering and how limit interacts with ranking.

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, no filler. The core capability is front-loaded in the first sentence and the corpus boundary follows as a separate, useful constraint.

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?

No output schema, but annotations carry the safety profile and the schema documents four of five parameters with formats and defaults. For a low-complexity search tool the description covers the essential framing; only result ordering and the meaning of limit remain unstated.

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 80%, so the baseline is 3. The description reinforces that matching applies to words and dates and clarifies the matched fields behind query, but it adds nothing for limit (no schema description) or date inclusivity beyond what the schema already states.

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 (поиск) and resource (новости), plus the exact scope searched: заголовок, анонс, текст, and dates. The archive start date ('с марта 2026 года') implicitly separates it from latest_news, but no sibling is named 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?

Usage is only implied: the archive framing ('Архив — с марта 2026 года') suggests this is the historical-search tool as opposed to latest_news or events, but the description never states when to prefer it or when not to use it.

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.

Resources