Skip to main content
Glama

Update lesson

update_course_lesson
DestructiveIdempotent

Updates a lesson title or rich-text description in the editable course draft.

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>",
      "patch": "<patch>"
    },
    "name": "update_course_lesson"
  }
}

Input Schema

NameRequiredDescriptionDefault
patchYes
course_idYes
lesson_idYes
idempotency_keyYes
expected_revisionYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, and idempotentHint=true, so the safety profile is covered. The description adds nothing beyond that: it does not say that existing title/description values are overwritten, nor that expected_revision guards against clobbering concurrent edits, nor how idempotency_key is replayed — all material for a destructive mutation.

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 or redundancy. It is compact, though at this level of brevity it verges on under-specification rather than exemplary conciseness.

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, draft-scoped mutation with five required parameters, a nested patch object, a concurrency token, an idempotency key, and no output schema, one sentence is not enough. An agent could invoke it, but without knowing the overwrite semantics or how expected_revision/idempotency_key must be sourced, correct invocation is guesswork.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across five required parameters, including a nested patch object, a revision token, and an idempotency key. The description only indirectly signals the patch fields (title, description) and says nothing about the meaning or use of expected_revision, idempotency_key, course_id, or lesson_id, so the compensation for the coverage gap is partial.

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 ("Updates a lesson title or rich-text description") and scopes it to the editable course draft, which separates it from published-course operations. It does not name the sibling that handles the article body (upsert_lesson_content), and "rich-text description" slightly muddies the field meaning, but an agent can identify the operation.

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?

"In the editable course draft" implies the tool only applies to draft state, which is useful when-to-use context. However, there is no explicit statement about when not to use it or which sibling to prefer for body content versus metadata, leaving the agent to infer alternatives from names.

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