Skip to main content
Glama

Remove lesson content

remove_lesson_content
DestructiveIdempotent

Removes the primary activity while preserving the lesson. Requires explicit typed user 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": "remove_lesson_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
course_idYes
lesson_idYes
idempotency_keyYes
confirmation_textYesMust exactly equal REMOVE CONTENT <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, idempotentHint=true and readOnlyHint=false, so the safety profile is largely covered. The description adds real value on top: it bounds the blast radius (the lesson survives, only its primary activity is removed) and imposes a typed-confirmation workflow step that the agent cannot learn from annotations.

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, front-loaded with the effect and then the precondition; nothing is padded. The only minor cost is the fuzzy noun 'primary activity', which could have been made concrete in the same space.

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 destructive, five-required-parameter mutation with no output schema and 80% undocumented schema, the description is too thin. It omits what happens on revision mismatch, how idempotency_key affects retries, and whether the removal is recoverable — all critical for a destructive call.

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 — and the description does not compensate for course_id, lesson_id, expected_revision, or idempotency_key. In particular, the meaning of the required expected_revision (an optimistic-concurrency guard) and idempotency_key are completely unstated anywhere.

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 ('Removes the primary activity') and adds a scope qualifier ('while preserving the lesson') that separates it from the lesson-deletion siblings such as delete_course_lesson. The term 'primary activity' is slightly vague, but the effect is unambiguous enough for an agent to select it.

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 definition gives a prerequisite ('Requires explicit typed user confirmation') which implies when the tool is callable, but it never states when to use this instead of delete_course_lesson or upsert_lesson_content. The agent must infer that distinction from sibling names alone.

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