Skip to main content
Glama

Create or edit course structure

apply_course_structure
DestructiveIdempotent

Adds or updates chapters and lessons in an unpublished course draft, including the first outline of an explicitly incremental course shell. Normal rich first drafts should begin with create_course_from_blueprint so source, activity, and dependency intent is durable. Set reorder to true and send every current chapter and lesson ID exactly once to apply the supplied order safely. Deletions use their dedicated confirmation-protected tools. It cannot create a course or publish.

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>",
      "expected_revision": "<expected_revision>",
      "idempotency_key": "<idempotency_key>",
      "chapters": "<chapters>"
    },
    "name": "apply_course_structure"
  }
}

Input Schema

NameRequiredDescriptionDefault
reorderNoWhen true, chapters and each chapter lessons are reordered to exactly match this complete list.
chaptersYes
course_idYes
idempotency_keyYes
expected_revisionYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already declare destructiveHint=true and idempotentHint=true. The description adds valuable context beyond those annotations by limiting operation to unpublished drafts, stating it cannot create or publish, and describing safe reorder behavior, though it does not explain revision-conflict or idempotency-key behavior.

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?

The description is dense but front-loaded: it states the core operation first, then alternatives, reorder safety, deletion routing, and limitations. Some phrasing such as 'explicitly incremental course shell' is compressed, but every sentence carries relevant guidance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, idempotent mutation tool with no output schema and only 20% schema coverage, the description covers usage and limitations well. It remains incomplete on concurrency semantics for expected_revision and on how idempotency_key should be chosen, which are important for calling this tool correctly.

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 20%, so the description must compensate for undocumented parameters. It explains reorder reasonably well, but gives no meaning for expected_revision, idempotency_key, course_id, client_ref, or the chapter/lesson object shapes beyond the schema's minimal field descriptions.

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?

The description states a specific verb and resource: it adds or updates chapters and lessons in an unpublished course draft. It explicitly separates this from create_course_from_blueprint, deletion tools, and course creation/publishing, so an agent can distinguish it from siblings.

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

Usage Guidelines5/5

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

It gives explicit routing guidance: normal rich first drafts should use create_course_from_blueprint, deletions should use dedicated confirmation-protected tools, and reorder requires every current chapter and lesson ID exactly once. It also states what the tool cannot do (create or publish a course).

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