Skip to main content
Glama

Delete course

delete_course
DestructiveIdempotent

Soft-deletes a course after explicit confirmation. This removes it from Academy use.

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>",
      "confirmation_text": "<confirmation_text>"
    },
    "name": "delete_course"
  }
}

Input Schema

NameRequiredDescriptionDefault
course_idYes
idempotency_keyYes
confirmation_textYesMust exactly equal DELETE COURSE <course_id> after the user confirms.
expected_revisionYes

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 declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The description usefully adds that this is a *soft* delete and that it removes the course from Academy use, but it omits the key behavioral fact an agent would want — whether a soft-deleted course can be restored, and what happens to chapters/lessons under it.

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?

Two short sentences with the destructive verb and the confirmation precondition front-loaded; no filler. It could have used the second sentence for a more load-bearing fact than 'removes it from Academy use', which is nearly implied by 'deletes'.

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?

This is an irreversible-looking destructive mutation with four required parameters and no output schema, yet the description never addresses recoverability, cascading effects on child content, or the meaning of expected_revision/idempotency_key. For that complexity level, the definition leaves too much for the agent to guess.

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?

With only 25% schema description coverage, three of four parameters (course_id, expected_revision, idempotency_key) are undocumented in both schema and description. The description gestures at confirmation but doesn't explain the confirmation_text format, the optimistic-concurrency role of expected_revision, or retry semantics of idempotency_key, 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?

States a specific verb and resource ('Soft-deletes a course') plus a qualifier ('removes it from Academy use'), which is far more informative than the title. It doesn't explicitly contrast with delete_course_chapter / delete_course_lesson, but the scope ('a course') is clear enough for an agent to distinguish.

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 'after explicit confirmation' implies a precondition, but only that the user must confirm — it says nothing about when to prefer this over the sibling delete tools or unpublish_course, nor when deletion is inappropriate. Usage is implied rather than stated.

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