Skip to main content
Glama

Удаление расписания записи

delete_scheduler
Destructive

Удаляет расписание записи вместе с его записями и блокировками времени — вернуть их нельзя. Если нужно просто перестать принимать записи, выключите расписание через save_scheduler (is_active).

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

Input Schema

NameRequiredDescriptionDefault
scheduler_idYesID расписания (из get_schedulers).
workspace_idYesID воркспейса (из workspace://list).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, so the irreversibility warning mostly restates structured data. The description does add genuinely non-annotated context – that associated bookings and time blocks are cascaded and cannot be restored – which is the main value here. It stops short of noting any authorization requirements or whether related data elsewhere is affected.

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?

Two tight sentences: the destructive effect with its cascade is front-loaded, then the alternative. No filler. Slightly dense for a two-line description but every clause carries information.

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?

For a two-parameter destructive tool with no output schema, an agent has what it needs: what is removed, that it is irreversible, and the safer alternative. Nothing material is missing.

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 coverage is 100% and both parameters already document their source (scheduler_id from get_schedulers, workspace_id from workspace://list). The description adds no further parameter meaning, so the baseline of 3 applies.

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?

States a specific verb and resource ("Удаляет расписание записи") and immediately scopes the effect: the schedule goes along with its bookings and time blocks. This is distinguishable from save_scheduler, which only toggles activity, without opening either schema.

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

Usage Guidelines5/5

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

Explicitly names the alternative and the condition that selects it: if the goal is merely to stop accepting bookings, use save_scheduler with is_active instead of deleting. That is a real when-not-to-use rule, not an implied one.

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