Skip to main content
Glama

Копия расписания записи

duplicate_scheduler

Копирует расписание записи. Настройки копируются, записи — нет: удобно завести похожее расписание с другой длительностью или другими часами.

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": "duplicate_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/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive creation. The description adds the genuinely valuable behavioral detail that settings are copied while existing bookings are not, which an agent could not infer from the annotations and which directly affects expectations about the new object.

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?

Two short sentences, zero waste, and the core purpose is front-loaded before the use case. Nothing needs to be trimmed or reordered.

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 simple two-parameter duplication tool with full annotation coverage and no output schema, the description covers what is copied, what is not, and a typical scenario. Minor gaps remain — whether the resulting schedule is enabled/published and whether repeat calls create additional copies.

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 (get_schedulers and workspace://list). The description adds no further meaning about how scheduler_id selects the source schedule or whether the copy inherits its active state, so it sits at the baseline.

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 gives a specific verb and resource — 'Копирует расписание записи' — so the agent knows exactly what is created. It does not name or contrast with a sibling such as save_scheduler or duplicate_quiz, so the sibling-differentiation credit is missing.

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 supplies a clear usage context: convenient for setting up a similar schedule with a different duration or different hours. That tells the agent when this tool is a good fit, but it gives no explicit when-not condition or named alternative (e.g., use save_scheduler to edit instead).

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