Skip to main content
Glama

Расписания записи на встречи

get_schedulers
Read-onlyIdempotent

Возвращает расписания записи на встречи: рабочие часы или слоты вручную, длительность встречи, буферы, лимиты и способ подтверждения. Расписание живёт на уровне аккаунта и подключается к опросам отдельно, поэтому одно расписание может обслуживать несколько опросов. Идентификаторы расписаний приходят только отсюда.

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

Input Schema

NameRequiredDescriptionDefault
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 readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds meaningful model context beyond that: schedules live at account level and are attached to surveys independently, so a single schedule may serve several surveys. It says nothing about pagination or result ordering, which is the remaining gap.

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, each earning its place: contents first, then the data model, then the critical ID-sourcing fact. No filler, no restatement of the title, and the most decision-relevant detail is placed last for emphasis.

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 single-parameter read tool with full schema coverage and no output schema, the description is essentially sufficient: it enumerates what comes back and explains the account-vs-survey relational model. Missing only whether the response is a list of all schedules and in what order.

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?

There is a single parameter with 100% schema description coverage (workspace_id pointing at workspace://list), so the schema already carries the semantics. The description adds no further detail about workspace_id or about how workspace scoping interacts with the account-level scheduling model. Baseline 3 applies when the schema does the work.

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 then enumerates what a schedule contains: работачие часы/слоты, длительность, буферы, лимиты, способ подтверждения. The final sentence ("Идентификаторы расписаний приходят только отсюда") makes the tool's unique role unmistakable against siblings like get_quiz_list that return other ID families.

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?

The description gives a clear usage signal: schedule IDs are only obtainable here, so an agent must call this before any tool that consumes a schedule ID. It also explains the account-level scope and the one-schedule-to-many-surveys relation, which guides interpretation. It stops short of naming an explicit alternative or a when-not-to-call condition.

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