Skip to main content
Glama

Создать курс

create_course

Заводит курс-черновик: ученикам он не виден, пока не опубликован через publish_course. Черновиков можно держать сколько угодно на любом тарифе. Режим доступа: open — всё открыто сразу, cohort — по расписанию потока, sequence — по прогрессу ученика. Автор курса — хозяин ключа. Повтор с тем же Idempotency-Key вернёт тот же курс, а не создаст второй.

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": {
      "title": "<title>"
    },
    "name": "create_course"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYes
access_modeNoopen
descriptionNo
Idempotency-KeyNoКлюч повтора, до 120 знаков. Новый на каждое новое создание; тот же, если повторяете этот вызов после ошибки или обрыва: второй раз ничего не создастся, вернётся первый ответ. Ключ помнится сутки.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / Idempotency-Key
      Added value: +{
      +  "description": "Ключ повтора, до 120 знаков. Новый на каждое новое создание; тот же, если повторяете этот вызов после ошибки или обрыва: второй раз ничего не создастся, вернётся первый ответ. Ключ помнится сутки.",
      +  "maxLength": 120,
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Goes well beyond the annotations: it discloses the resulting state (draft, hidden from students), quota behavior (unlimited drafts on any plan), ownership semantics (the author is the key owner), and retry semantics (same Idempotency-Key returns the same course rather than creating a second). The key-based dedup sits alongside idempotentHint=false, which is consistent because without the key a repeat would create a duplicate; the description clarifies that mechanism rather than contradicting it.

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?

Front-loads the most decision-relevant fact (draft, not visible, published via publish_course) before the secondary details. Every sentence carries distinct information — visibility, quota, access modes, ownership, idempotency — with no restatement of the name or 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 4-parameter creation tool with an output schema (so return values need no explanation), this covers state, quota, access modes, ownership, and retry behavior. It could be slightly more complete by noting whether title must be unique or what happens on validation failure, but nothing essential to a correct first call is missing.

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 only 25%, so the description has to compensate, and it does so for the two non-obvious parameters: all three access_mode values are defined inline ('open' = everything open at once, 'cohort' = by cohort schedule, 'sequence' = by student progress), and the retry contract of Idempotency-Key is restated with its effect. Title and description remain self-explanatory from the schema, so the remaining gap is minor.

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?

Opens with a specific verb+resource: it creates a draft course ('Заводит курс-черновик'), and immediately states the key scope fact that it is invisible to students until published. It also names the sibling that performs that transition ('publish_course'), so an agent can distinguish create from publish 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 Guidelines4/5

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

Gives clear usage context: drafts are unlimited on any tariff, and publishing is a separate step handled by publish_course. It does not spell out when-not-to-use (e.g. when a course with the same title already exists, or when to use list_courses first to check), so it stops short of explicit exclusions.

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