Skip to main content
Glama

Move course lesson

move_course_lesson
Idempotent

Moves an existing lesson to a position in the same or another chapter of the editable draft.

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>",
      "lesson_id": "<lesson_id>",
      "target_chapter_id": "<target_chapter_id>",
      "expected_revision": "<expected_revision>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "move_course_lesson"
  }
}

Input Schema

NameRequiredDescriptionDefault
positionNoZero-based position in the target chapter. Omit or use null to append.
course_idYes
lesson_idYes
idempotency_keyYes
expected_revisionYes
target_chapter_idYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=true), so the bar is lower, and the description usefully adds the key constraint that this only touches the editable draft. However, it says nothing about what happens to sibling lessons' positions, whether the move is reversible, or how concurrency conflicts surface.

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?

A single front-loaded sentence with no filler and no redundant restatement of the title. It is efficient, though its brevity comes at the cost of the operational details an agent needs.

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 6-parameter, 5-required mutation with no output schema and sparse schema descriptions, the definition is too thin: it gives no guidance on revision matching, idempotency key reuse, or the append-by-default positioning semantics that the schema implies. The draft-only scope is the one important context it does supply.

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 17% — just the optional position field — and the description does not compensate, leaving expected_revision and idempotency_key completely unexplained in both structured and prose form. It only loosely hints at target_chapter_id by mentioning moving between chapters of the draft; for an optimistic-concurrency mutation, the unexplained expected_revision and idempotency_key are a meaningful 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?

States a specific verb and resource ("Moves an existing lesson to a position") plus the target scope ("same or another chapter of the editable draft"), which naturally separates it from update_course_lesson or delete_course_lesson. It stops short of naming any alternative, so the differentiation relies on the verb alone.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance and no mention of prerequisites such as the course needing to be in draft state or the lesson already existing. The single clause "of the editable draft" implies the operating context but does not tell an agent what to do when the course is published or already mid-build.

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