Skip to main content
Glama

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

create_module

Модуль встаёт в конец курса. Уроки добавляются в модуль отдельно, create_lesson. Порядок модулей потом можно поменять в кабинете.

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

Input Schema

NameRequiredDescriptionDefault
titleYes
course_idYes
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

A3.6/5.0
Behavior4/5

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

Beyond annotations (readOnly=false, destructive=false, idempotent=false, openWorld=false), the description discloses meaningful behavior: the new module is appended to the end of the course, and its ordering is mutable later in the admin panel — which signals reversibility of the positional side effect. It does not mention the idempotency-key retry semantics present in the schema, but that is already documented there.

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, zero filler, and the most decision-relevant fact (append-at-end behavior) is front-loaded. Each sentence adds distinct information: placement, the follow-up lesson step, and later reordering.

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 annotations covering the safety profile and an output schema present, the description only needs to explain placement and sequencing — which it does. The remaining weakness is the unexplained required parameters, but their names are largely self-evident for an agent familiar with the course domain.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33%: only `Idempotency-Key` is annotated, while `course_id` and `title` carry no schema description. The description refers to "курса" generically but never explains which course identifier is expected or any constraints on the module title (e.g., the 1–200 character bounds), so it fails to compensate for the coverage gap.

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 makes clear that a module is created and placed at the end of a course ("Модуль встаёт в конец курса"), which pairs with the tool name create_module to give a specific verb+resource. It also distinguishes the lesson-creation step by naming `create_lesson`. The only gap is that the act of creation itself is implied by placement rather than stated outright.

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?

It gives a useful sequencing hint: a course must exist and lessons are added afterwards via `create_lesson`. However, there is no explicit when-to-use/when-not guidance and no prerequisites such as required permissions or whether the course must be non-archived. Usage is implied rather than directed.

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