Skip to main content
Glama
Sign In

TenQueue

by com.tenqueue
OverviewDiscussionsAdmin

Update quiz

update_quiz
Destructive

Changes data. Replace the questions/title/teams of an existing quiz with the maker's approved changes. Pass expected_version from get_quiz; a version conflict means the quiz changed elsewhere (e.g. in the editor): fetch again and merge. Keep unchanged questions and existing mediaUrl values. A live game that has not started is updated too.

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": {
      "quiz_id": "<quiz_id>",
      "expected_version": "<expected_version>",
      "quiz": "<quiz>"
    },
    "name": "update_quiz"
  }
}

Input Schema

NameRequiredDescriptionDefault
quizYesThe whole quiz after the change: title, language, teams and every question, including the unchanged ones
quiz_idYesquiz_id returned by create_quiz or list_quizzes
expected_versionYesversion from get_quiz

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, but the description adds real context beyond them: optimistic concurrency via expected_version, the meaning of a conflict, full-replacement semantics requiring unchanged questions and existing mediaUrl to be preserved, and the side effect on a live game that has not started.

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?

Sentences are dense and front-loaded, moving from action to conflict handling to preservation rules to the live-game side effect. The generic opener 'Changes data.' is the only sentence that does not earn its place.

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-schema mutation with no output schema, the description covers the risky parts: concurrency, replacement scope, media preservation, and live-game impact. It stops short of describing the success response or how publish state is affected.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline would be 3, but the description adds meaning beyond the schema by explaining what expected_version guards against and how to recover, plus reinforcing that the quiz payload is a whole-quiz replacement rather than a patch.

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 description states a specific verb and resource: replacing questions/title/teams of an existing quiz with the maker's approved changes. 'Existing quiz' implicitly distinguishes it from create_quiz, 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 clear conditions: apply the maker's approved changes, pass expected_version from get_quiz, and on version conflict fetch again and merge. It does not name named alternatives such as validate_quiz or preview_quiz, so the routing is implied rather than explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All TenQueue toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources