Skip to main content
Glama

Правка записи на встречу

update_booking
Destructive

Занятость слота при переносе не проверяется: сначала посмотрите журнал через get_booking_journal. Изменяет запись: подтвердить, отменить, отметить неявку или перенести на другое время. Перенос требует обе границы — начало и конец. Респондент получит письмо, если в расписании включены уведомления.

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>",
      "booking_id": "<booking_id>"
    },
    "name": "update_booking"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusNopending, confirmed, cancelled или no_show.
commentNoКомментарий к записи.
end_utcNoНовый конец встречи в UTC, передаётся вместе с началом.
start_utcNoНовое начало встречи в UTC, например 2026-10-01T09:00:00Z. Время без пояса тоже считается UTC.
booking_idYesID записи (из get_booking_journal).
workspace_idYesID воркспейса (из workspace://list).

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?

Goes well beyond the annotations: discloses that slot occupancy is NOT validated on reschedule (a destructive side effect the agent could otherwise cause unknowingly), and that the respondent receives an email if schedule notifications are enabled. This is exactly the kind of consequence context that destructiveHint=true alone cannot convey.

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?

Four short sentences, front-loaded with the highest-risk caveat (no slot check) followed by the action list, the reschedule constraint, and the notification side effect. No filler or restatement of the title.

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 destructive, non-idempotent mutation with no output schema, the description covers prerequisites, action semantics, parameter coupling, and a user-visible side effect. Missing only auth/permission expectations and what a successful response contains, which is minor given the annotations.

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 baseline would be 3, but the description adds meaning: it clarifies that start_utc and end_utc must be supplied together as a pair for a reschedule, and frames status as one of four named actions. The comment parameter and timezone nuance remain schema-only.

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?

Names a specific verb+resource ('Изменяет запись') and enumerates the exact operations available: confirm, cancel, mark no-show, reschedule. An agent can distinguish it from get_booking_journal (read) and create_booking_block without opening any schema.

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?

Explicitly routes the agent to get_booking_journal first before rescheduling, and states the prerequisite condition (slot availability is not verified). It gives no guidance on when to prefer a different mutation tool or when not to use this one, but the key sequencing advice is present and actionable.

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