moodle-um

moodle_quiz_submit

Submits a finished Moodle quiz attempt permanently and irreversibly. Call only with confirm=true after showing answers and receiving explicit user approval.

Instructions

Finish and submit a quiz attempt. IRREVERSIBLE.

Only call with confirm=true after showing the user the answers and getting an explicit "yes".

Args: attemptid: quiz attempt id. page: optional zero-based page number. confirm: must be true.

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": {
      "attemptid": "<attemptid>"
    },
    "name": "moodle_quiz_submit"
  }
}

Input Schema

Name	Required	Description	Default
`page`	No
`confirm`	No
`attemptid`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.1Nov 12, 2026

TDQS

A4/5.0

Behavior4/5

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

With no annotations supplied, the description carries the full behavioral burden and does disclose the most important trait: the operation is irreversible and gated by a confirmation flag plus user consent. It does not say what is returned or what state the attempt is in afterward, so it is strong but not complete.

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?

The warning is front-loaded in the first two lines, and the Args block is compact with no filler. The schema-style arg listing is mildly mechanical but justified given 0% schema coverage.

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 3-parameter irreversible mutation with no annotations and no output schema, the definition covers the safety gate, the consent protocol, and every parameter. The main residual gap is the absence of any statement about the post-submit result or error conditions.

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 description coverage is 0%, and the description compensates by explaining all three parameters: attemptid as the quiz attempt id, page as an optional zero-based page, and confirm as mandatory-true. It never explains what page affects during a submission, which keeps it below a 5.

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 ('Finish and submit a quiz attempt') plus a consequence marker ('IRREVERSIBLE'), which lets an agent separate it from moodle_quiz_start or moodle_quiz_solve. It never names a sibling explicitly, so it stops short of the top band.

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 precondition for invocation: only call with confirm=true after showing the user the answers and receiving an explicit 'yes'. That is clear when-to-use guidance, though no alternative tool is named for the case where the user has not yet answered.

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