Skip to main content
Glama

МАРШРУТ — Байкал и Россия

search_stays

Read-only

Подобрать жильё и развлечения МАРШРУТА: город, тип (отель, гостевой дом, база отдыха, баня…), слово для поиска, максимальная цена «от» в рублях, число гостей. Возвращает варианты со ссылками.

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

Input Schema

NameRequiredDescriptionDefault
cityNoГород или место, например «Листвянка»
typeNoТип: отель, гостевой дом, база отдыха, баня…
limitNo
queryNoСлово для поиска в названии и описании
guestsNo
checkinNoДата заезда ГГГГ-ММ-ДД (необязательно)
checkoutNoДата выезда ГГГГ-ММ-ДД (необязательно)
max_priceNoЦена «от» не выше, ₽

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that results are 'варианты со ссылками', which is useful return information, but it says nothing about the limit/pagination behavior or the date-range filtering that the schema exposes.

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 purpose and a compact field list, with the return note last. The parenthetical type examples earn their place, though the field enumeration partly duplicates the schema.

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 an 8-parameter search tool with no output schema, the description covers purpose and result form adequately but leaves the date parameters (checkin/checkout) and limit unaddressed, even though date filtering is central to lodging search. Annotations carry the safety side, keeping this at a minimum-viable level.

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?

Schema coverage is already 75%, but the description still adds meaning by glossing max_price as 'цена «от» не выше' and giving examples for the type field (отель, гостевой дом, база отдыха, баня). It omits checkin, checkout and limit entirely, which are non-trivial for a stay search.

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 ('жильё и развлечения МАРШРУТА') and enumerates the discriminating filters (city, type, query, max_price, guests), so an agent knows it is a lodging/entertainment search. It stops short of naming how it differs from siblings like get_place or search_companions.

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 by the listed search dimensions; there is no explicit statement of when to pick this over get_place or prepare_booking, nor any exclusion (e.g. 'does not book'). The agent must infer the routing from the sibling names.

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