Skip to main content
Glama
EduBase

EduBase MCP Server

Official
by EduBase
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

edubase_post_exam_round

Start a new exam round: close active tests, detach previous results, reset accounts, and enable another group of examinees to retake the exam.

Instructions

Start a new round of the exam. The running tests are closed, the results of the previous round are detached from the exam accounts and the generated accounts are reset, so the exam can be taken again by another group of examinees. A new round cannot be started when the exam is locked, archived, the current round is frozen (see the freeze_round setting of edubase_post_exam_settings), or the results viewing period of the exam has already begun (see the view_results_start setting of edubase_post_exam_settings).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
examYesexam identification string
forceNostart a new round even if the current one has no results yet (default: false)
notifyNonotify the assigned users about the exam (default: false)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
examYes
roundYes
frozenYes
resultsYes
startedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv2.0.0
    • removedOutput schema / properties / exam / description
      Removed value: -"exam identification string"
    • removedOutput schema / properties / frozen / description
      Removed value: -"the current round is frozen, no new round can be started"
    • removedOutput schema / properties / results / description
      Removed value: -"the current round already has results"
    • removedOutput schema / properties / round / description
      Removed value: -"index of the current round"
    • removedOutput schema / properties / started / description
      Removed value: -"date and time the current round was started at"
  2. Addedv1.2.15

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations, the description discloses concrete side effects: running tests are closed, previous results are detached from exam accounts, and generated accounts are reset. It also surfaces state-dependent gotchas with references to the exact settings that control them. This is exactly the kind of behavioral context agents need, and it does not contradict the annotations.

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?

The description is three sentences with no filler: the main action is front-loaded, followed by a compact list of side effects, then a concise list of blocking conditions. The references to edubase_post_exam_settings settings are precise and earn their place.

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

Completeness5/5

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

Given the rich schema, the output schema, and the detailed behavioral description, nothing essential is missing for an agent to invoke this tool correctly. The description covers what happens, when it cannot happen, and which settings govern the constraints, making it complete for this mutation operation.

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 100%, and each parameter has its own inline description, so the baseline of 3 applies. The tool description does not add parameter-level detail beyond the schema, though it does help contextualize the 'no results yet' state that the force parameter relates to.

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 resource: 'Start a new round of the exam.' It then details the lifecycle effects—closing running tests, detaching results, and resetting generated accounts—which makes the operation unambiguous and distinct from other exam-related sibling tools like get_exam_round or post_exam_settings.

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?

The description gives strong contextual guidance by stating when the tool is appropriate (after a previous round, to let another group take the exam) and explicit disqualifiers: locked, archived, frozen round, or results viewing period started. It does not name an alternative tool to use instead, so it stops short of a full 5.

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

Deploy Server

Other Tools