Skip to main content
Glama

Снятие блокировки времени

delete_booking_block
Destructive

Снимает блокировку и снова открывает время для записи.

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>",
      "block_id": "<block_id>"
    },
    "name": "delete_booking_block"
  }
}

Input Schema

NameRequiredDescriptionDefault
block_idYesID блокировки (из get_booking_journal, ключ blocks).
workspace_idYesID воркспейса (из workspace://list).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and readOnlyHint=false, so the safety profile is carried. The description adds the post-condition that the time slot becomes bookable again, which is useful beyond the annotations, but it omits what is lost, whether existing bookings are affected, permission requirements, and irreversibility.

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?

A single front-loaded sentence with zero filler, and the effect is stated in the predicate. It is efficient, though the extremely short length is part of why other dimensions lack depth.

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 a simple two-parameter, non-open-world tool with no output schema, the description is sufficient for correct invocation since the schema documents both IDs. However, for a destructive, non-idempotent mutation it should say more about consequences and re-invocation behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and the schema already documents both block_id and workspace_id with provenance hints (get_booking_journal blocks key, workspace://list). The description adds no meaning beyond the schema, so the 100%-coverage baseline of 3 applies.

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 names a specific verb and resource ("Снимает блокировку") and states the resulting state ("снова открывает время для записи"), which lets an agent distinguish it from create_booking_block as the inverse operation. It does not explicitly name that sibling, so differentiation is inferred rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no prerequisites, and no exclusions or named alternatives. An agent must deduce from the name alone that this is the undo counterpart to create_booking_block and when unblocking is appropriate.

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