Skip to main content
Glama

Добавить урок в модуль

create_lesson

Урок встаёт в конец модуля. document — в формате TipTap ({"type": "doc", "content": [{"type": "heading", "attrs": {"level": 2}, "content": [{"type": "text", "text": "..."}]}, {"type": "paragraph", "content": [...]}]}); узлы перечислены у get_lesson, образец отдаёт он же. Старый формат Editor.js ({"blocks": [...]}) тоже принимается и переводится. Видео — провайдер и идентификатор, не iframe. Неизвестное выбрасывается.

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

Input Schema

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

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

A3.8/5.0
Behavior4/5

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

Annotations already mark this as a non-destructive write, and the description adds real behavioral detail on top: ordering (always last in module), silent dropping of unknown fields, legacy Editor.js payloads being converted, and the rule that video must be provider+identifier rather than an iframe. This is genuinely useful mutation context beyond the structured fields.

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?

Ordering behavior is front-loaded, then the document format, then the video and unknown-field caveats. Dense but every sentence carries information; the inline JSON example is long but earns its space by defining the payload shape.

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?

With an output schema present, the description need not explain return values, and it covers the one ambiguous input (document) and the lossy behaviors. Missing only guidance on the idempotency key, whose semantics live entirely in the schema and are not reinforced at the description level.

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 14%, so the description has to compensate, and it does so for the hardest parameter: the full TipTap document shape with an inline example plus the accepted Editor.js fallback. kind, title, module_id, is_required and duration_minutes get no description-level explanation, but they are conventional and typed in the schema.

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 pairs the creation verb with the resource and states a concrete scoping behavior: the lesson is appended to the end of the module. It is clear what the call produces, though it never separates itself from update_lesson or create_test by name.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: it is a create call that needs a module_id and title, and get_lesson is named only as a reference for valid node types, not as an alternative to choose between. No when-not-to-use guidance or prerequisites are given.

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