Skip to main content
Glama

Update course draft

update_course_draft
DestructiveIdempotent

Updates course metadata, authors, learner settings, or removes the current cover. Enable certification only when the user asks, and send the certificate name and signing authority they gave. It does not alter course structure, lesson content, or publishing.

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

Input Schema

NameRequiredDescriptionDefault
patchYes
course_idYes
idempotency_keyYes
expected_revisionYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare the mutation profile (readOnlyHint=false, destructiveHint=true, idempotentHint=true), so the description only needs to add context, and it does: it discloses the destructive cover-removal path and states the certification policy that the tool will not act on unless the user requests it. It omits any mention of revision conflict handling or what a stale expected_revision produces, which is a meaningful behavioral gap for a concurrent-edit tool.

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?

Three sentences, each doing distinct work: scope, conditional policy, and exclusions. The constraint that matters most is front-loaded, and nothing is repeated from the annotations.

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

Completeness4/5

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

For a destructive, nested-patch mutation with no output schema, the definition covers scope, policy conditions, and exclusions adequately. The remaining shortfall is the unexplained revision/idempotency contract, which matters given the tool is declared idempotent and requires expected_revision.

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?

The description maps well onto the patch surface (metadata, authors, settings, certification, cover), which compensates for the reported low top-level schema coverage. However, three required top-level parameters — course_id, expected_revision, and idempotency_key — receive no explanation in either the description or the schema, so an agent gets no guidance on concurrency or retry semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and enumerates the exact surfaces touched (course metadata, authors, learner settings, cover removal), then draws a hard boundary against siblings: 'It does not alter course structure, lesson content, or publishing.' That boundary cleanly separates it from apply_course_structure, update_course_lesson, and publish_course.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Enable certification only when the user asks, and send the certificate name and signing authority they gave' is an explicit when-to-use condition with an input-provenance rule, and the negative scope steers agents away from structural edits. It stops short of naming the sibling tools to use for structure, lessons, or publishing, leaving that routing implicit.

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