Skip to main content
Glama

Create or update lesson task

upsert_lesson_task
DestructiveIdempotent

Creates or updates a learner task as the lesson primary activity. Updating the same task is direct; replacing another activity requires the returned confirmation token and a new idempotency key.

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>",
      "task": "<task>"
    },
    "name": "upsert_lesson_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskYes
course_idYes
lesson_idYes
idempotency_keyYes
expected_revisionYes
replacement_confirmation_tokenNo

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already flag destructiveHint and idempotentHint, but the description adds real value by explaining that a replace path is gated behind a confirmation token and a fresh idempotency key, which tells the agent the idempotency hint does not hold across replacements. It still does not say what data is lost when another activity is replaced.

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?

Two short sentences, front-loaded with the create/update distinction, and every clause carries information an agent needs. No filler.

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?

A destructive, non-idempotent-across-replacements mutation with six parameters (five required, one nested object) and no output schema demands more. The confirmation-token flow is explained, but the concurrency-control parameter expected_revision and the entire task payload shape are left 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 0%, so the description must carry the load and largely fails: expected_revision, course_id, lesson_id, and all nested task fields (title, instructions_html, review_mode) are untouched. It only gestures at idempotency_key and replacement_confirmation_token, leaving four parameters with no meaning anywhere in the definition.

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 ('Creates or updates a learner task') and adds scope ('as the lesson primary activity'). It does not explicitly distinguish itself from siblings such as upsert_lesson_quiz or upsert_lesson_content, so it stops short of a 5.

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?

Gives an explicit decision rule: updating the same task is direct, while replacing a different activity requires the returned confirmation token plus a new idempotency key. It covers the two paths for this tool but never names the sibling tools it competes with.

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