Skip to main content
Glama

Create or update lesson quiz

upsert_lesson_quiz
DestructiveIdempotent

Atomically creates or replaces a complete lesson quiz. Updating the same quiz is direct; Generate questions from the lesson content and user goal, present them for approval when intent is ambiguous, then save the complete quiz. Choice refs may repeat between questions because Trainn namespaces them. 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>",
      "quiz": "<quiz>"
    },
    "name": "upsert_lesson_quiz"
  }
}

Input Schema

NameRequiredDescriptionDefault
quizYes
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?

Beyond the annotations (destructiveHint=true, idempotentHint=true), it discloses atomicity, the token-gated replacement path, and the requirement for a fresh idempotency key, which materially changes how an agent sequences the call. It does not say what the token-issuing response looks like or what reverting a replacement does.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening is front-loaded and tight, but the second sentence is garbled: 'Updating the same quiz is direct; Generate questions from the lesson content and user goal...' splices an unrelated workflow instruction mid-thought with a stray capital, forcing the reader to re-parse.

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?

For a 6-parameter nested mutation with no output schema, the description covers the safety and idempotency mechanics well but omits the revision-conflict contract and the shuffle_questions behavior, both relevant to calling it correctly. Adequate, not complete.

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%, so the description must carry parameter meaning, and it only partially does: it covers idempotency_key and replacement_confirmation_token behaviorally and clarifies that choice refs may repeat because they are namespaced. Required parameters expected_revision (clearly an optimistic-concurrency token), shuffle_questions, and the course/lesson scoping are left unexplained.

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?

The first sentence gives a specific verb pair plus resource and an atomicity guarantee: 'Atomically creates or replaces a complete lesson quiz.' That distinguishes it from sibling upserts such as upsert_lesson_content and upsert_lesson_task, though no sibling is named explicitly.

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?

It gives conditional routing: updating the same quiz is direct, while replacing a different activity requires the returned confirmation token plus a new idempotency key, and ambiguous intent should trigger approval before saving. It stops short of explicit when-not-to-use or named alternatives.

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