Skip to main content
Glama

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

Свободное время

get_available_slots
Read-onlyIdempotent

Free start times for a service, in the salon's time zone, for up to 7 days starting at dateFrom (default today), optionally for one master. The salon's own rules apply (minimum notice, how far ahead one may book). Returns at most 60 times grouped by date, with masters free at each time, and the bookingUrl where the person picks the time and books.

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": {
      "serviceId": "<serviceId>"
    },
    "name": "get_available_slots"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoHow many days, 1–7 (default 3).
dateFromNoFirst day, YYYY-MM-DD, in the salon's time zone. Default: today.
masterIdNoOnly this master (id from the service's masters).
serviceIdYesService id from search_services or get_salon.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, closed-world, non-destructive), it discloses real behavioral traits: the salon's own minimum-notice and booking-horizon rules constrain results, output is capped at 60 times grouped by date, and each time lists the masters free at that moment. That is exactly the kind of context annotations cannot carry.

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?

The scope constraint and defaults are front-loaded in the first sentence, and the return-shape sentence follows logically. It is a single dense paragraph; the parenthetical about salon rules is slightly compressed, but no sentence is wasteful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the return-shape burden itself and does so — result cap, grouping by date, masters per slot, and the bookingUrl. Combined with the parameter schema, an agent has enough to call it correctly and interpret the response.

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 100%, so all four parameters are documented in structured form; the description adds the interpretive nuance that dateFrom is interpreted in the salon's time zone and that masterId is optional rather than an implicit filter. It stops short of adding format or validation detail beyond the schema, so it is a modest improvement over baseline.

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?

The description names a specific resource (free start times for a service) with explicit scope: salon time zone, up to 7 days from dateFrom, optionally filtered to one master. It is clearly distinguishable from siblings like prepare_booking or get_salon, which do not return availability.

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?

It establishes the practical context for calling it — default window is today plus up to 7 days, default master scope is all masters — and its mention of bookingUrl implies this is the discovery step before booking. It does not, however, explicitly state when to prefer it over prepare_booking or what to do when zero slots come back.

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