Skip to main content
Glama

uPlanny — салоны и запись

Поиск услуг

search_services
Read-onlyIdempotent

Search services across all businesses: «маникюр с покрытием до 2000 ₽ рядом с метро Сокол с рейтингом от 4.5». Separate rating bounds for the salon, for the service itself and for its masters (a master bound matches when at least one master performing the service is rated within it). Price bounds apply to the service price (RUB). Each item: serviceId (for get_available_slots), name, durationMinutes, price, rating, masters with their ratings, the salon (slug, name, address, rating, distanceKm) and bookingUrl.

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

Input Schema

NameRequiredDescriptionDefault
latNoLatitude of the place to search around (instead of `near`).
lngNoLongitude of the place to search around (instead of `near`).
cityNoOnly businesses whose address contains this text, e.g. a city «Казань». Ignored when a place is given.
nearNoA place to search around: address, metro station or landmark, with the city — «Москва, метро Сокол», «Казань, Баумана 10». Used for «рядом», «около», «недалеко», «поблизости».
pageNoPage number, from 0.
sortNoOrder. Default: distance when a place is given, otherwise the service's rating.
queryNoWhat the service is, in Russian: «маникюр», «стрижка», «массаж спины», «окрашивание».
categoryNoCategory id from list_categories.
maxPriceNoService price at most this, RUB.
minPriceNoService price at least this, RUB.
pageSizeNoItems per page, 1–20 (default 10).
radiusKmNoSearch radius around the place, km (default 3, max 50; ~1 for «в шаговой доступности»).
minReviewsNoWith a rating bound: at least this many reviews behind each bounded rating (default 1).
maxSalonRatingNoSalon rating at most (1–5).
minSalonRatingNoSalon rating at least (1–5).
maxMasterRatingNoSome master of the service rated at most (1–5).
minMasterRatingNoSome master of the service rated at least (1–5).
maxServiceRatingNoRating of this service at most (1–5).
minServiceRatingNoRating of this service at least (1–5).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish readOnlyHint, idempotentHint, non-destructive and closed-world behavior. The description adds substantive context: master rating bounds match when at least one performing master is in range, price bounds apply to service price in RUB, and each result includes masters, salon details and bookingUrl.

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?

Front-loads the tool purpose, uses a compact example to encode a multi-filter query, then explains only the non-obvious rating/price semantics and return shape. It avoids redundant restatement of schema fields.

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 19-parameter search tool with no output schema, the description supplies the result item structure and the key filter semantics. It leaves alternative-tool routing to usage guidance but is otherwise sufficient for correct invocation.

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?

With 100% schema description coverage, the baseline is 3. The description adds non-obvious meaning about the three separate rating bound families and the master-bound matching rule, plus confirms that price bounds apply to the service price rather than the salon.

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 ('Search services across all businesses') and gives a concrete multi-filter example. It does not name search_salons or explicitly contrast service-level search with salon-level search, so sibling differentiation is only indirect.

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?

The example illustrates a natural use case and the returned serviceId points to get_available_slots, but there is no explicit when-to-use or when-not-to-use guidance versus siblings such as search_salons or list_categories. Usage is implied rather than spelled out.

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