Skip to main content
Glama

Delete course chapter

delete_course_chapter
DestructiveIdempotent

Permanently removes a chapter and all of its lessons 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>",
      "chapter_id": "<chapter_id>",
      "expected_revision": "<expected_revision>",
      "idempotency_key": "<idempotency_key>",
      "confirmation_text": "<confirmation_text>"
    },
    "name": "delete_course_chapter"
  }
}

Input Schema

NameRequiredDescriptionDefault
course_idYes
chapter_idYes
idempotency_keyYes
confirmation_textYesMust exactly equal DELETE CHAPTER <chapter_id> after the user confirms.
expected_revisionYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.5/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 safety profile is covered. The description still adds real value beyond them: it discloses permanence, the cascade to lessons, that it acts on the editable draft only, and the confirmation requirement.

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?

A single front-loaded sentence with no filler. The most decision-relevant facts (permanence, cascade, draft scope, confirmation) all appear immediately.

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?

The cascade and draft-only scope are covered, which matters for a destructive mutation. However, with five required parameters at 20% schema coverage and no output schema, the description leaves the revision and idempotency requirements unexplained.

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%: only confirmation_text is documented in the schema. The description alludes to confirmation but does not explain expected_revision (concurrency guard), idempotency_key, or the course/chapter identifiers, so it fails to compensate for the undocumented parameters.

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 states a precise verb and resource ("Permanently removes a chapter and all of its lessons") and adds scope that distinguishes it from delete_course_lesson by disclosing the cascade. It does not name a sibling alternative explicitly, but the cascading scope makes the distinction inferable.

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?

The phrase "from the editable draft" implies when this applies (draft editing rather than published content), and "after explicit confirmation" sets a precondition. There is no explicit guidance on when to pick this over delete_course_lesson or delete_course, and no stated exclusions.

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