Skip to main content
Glama

Delete lesson

delete_course_lesson
DestructiveIdempotent

Permanently removes one lesson from the editable draft after explicit confirmation.

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>",
      "expected_revision": "<expected_revision>",
      "idempotency_key": "<idempotency_key>",
      "confirmation_text": "<confirmation_text>"
    },
    "name": "delete_course_lesson"
  }
}

Input Schema

NameRequiredDescriptionDefault
course_idYes
lesson_idYes
idempotency_keyYes
confirmation_textYesMust exactly equal DELETE LESSON <lesson_id> after the user confirms.
expected_revisionYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the description is not required to establish irreversibility. It still adds real value by confirming permanence, restricting scope to the draft, and flagging that explicit user confirmation must precede the call — a prerequisite annotations do not express.

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; permanence and scope come first. It is efficient, though the extreme brevity is part of why the parameter and precondition detail is thin.

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

Completeness2/5

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

For a five-required-parameter destructive mutation with no output schema and 20% schema coverage, the definition is thin. An agent gets the safety story but not how to supply or refresh expected_revision, why an idempotency_key is mandatory, or what happens on a revision mismatch.

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%, with confirmation_text the sole documented parameter, so the description needs to compensate and largely does not. It gestures at the confirmation requirement but says nothing about expected_revision (optimistic concurrency) or idempotency_key, both required and non-obvious.

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 ('Permanently removes one lesson') and scopes it to 'the editable draft', which separates it from delete_course and delete_course_chapter. It never names a sibling explicitly and does not distinguish itself from remove_lesson_content, which likely targets a different unit of content.

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?

'From the editable draft' implies the tool only applies to drafts, and 'after explicit confirmation' implies a workflow precondition. There is no explicit when-not guidance (e.g., published courses) and no pointer to the sibling that removes lesson content rather than the lesson itself.

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