Skip to main content
Glama

Блокировка времени записи

create_booking_block

Закрывает промежуток для записи — отпуск, занятое окно, выходной. Уже сделанные записи он не отменяет. Границы задаются в UTC: часовой пояс расписания и пояс респондента различаются, и UTC — единственный способ не промахнуться.

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": {
      "workspace_id": "<workspace_id>",
      "scheduler_id": "<scheduler_id>",
      "start_utc": "<start_utc>",
      "end_utc": "<end_utc>"
    },
    "name": "create_booking_block"
  }
}

Input Schema

NameRequiredDescriptionDefault
commentNoПочему время закрыто.
end_utcYesКонец закрытого промежутка в UTC.
start_utcYesНачало закрытого промежутка в UTC, например 2026-10-01T09:00:00Z. Время без пояса тоже считается UTC.
scheduler_idYesID расписания (из get_schedulers).
workspace_idYesID воркспейса (из workspace://list).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare this as a non-read-only, non-destructive, non-idempotent write, so the bar is lower. The description still adds real behavioural value by clarifying that existing bookings survive the block — the single most likely misinterpretation of 'Закрывает' — and by explaining the UTC requirement rather than merely stating it. It stops short of describing what happens to pending/overlapping bookings or any permission requirements.

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?

Three short sentences with zero filler: purpose first, then the non-cancellation caveat, then the timezone rule. Each sentence carries a distinct, decision-relevant fact and is ordered by importance.

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 four-required-parameter write with no output schema and fully described parameters, the description covers purpose, side effects, and the one input convention most prone to error. The remaining gaps — overlap behaviour, permissions, and what the call returns — are modest given the annotation set but keep it from being fully complete.

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 the baseline would be 3. The description earns above baseline by explaining why both boundaries must be UTC: the schedule timezone and the respondent timezone diverge, making UTC the only safe convention — that rationale directly reduces a common off-by-timezone error that the schema fields only assert, not justify.

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 gives a concrete verb and resource ('Закрывает промежуток для записи') and names the concrete scenarios (vacation, busy window, day off) that define the resource. It also states what the tool is not ('Уже сделанные записи он не отменяет'), which implicitly separates it from cancel/delete behaviour on the same resource.

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 use cases (vacation, occupied slot, day off) make the intended situation clear, so the usage context is real rather than implied by the name alone. However, it never routes the agent to or away from siblings such as delete_booking_block or update_booking, and gives no prerequisites (e.g. which IDs come from which lookup, or what to do if a block already covers the range).

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