Skip to main content
Glama
EduBase

EduBase MCP Server

Official
by EduBase
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

edubase_post_exam

Schedule a new exam from an existing Quiz set. Provide title, quiz, and start/end times to create a time-constrained assessment instance.

Instructions

Create a new exam from an existing Quiz set. Exams are at the top level of the EduBase Quiz hierarchy and MUST be created from existing Quiz sets. They are time-constrained, secured assessment instances of Quiz sets.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoexternal unique exam identifier
endYesexam end time (in YYYY-MM-DD HH:ii:ss format)
quizYesthe Quiz set (specified using the Quiz identification string) the exam is attached to
typeNotype of the exam (default: exam)
startYesexam start time (in YYYY-MM-DD HH:ii:ss format)
titleYestitle of the exam
languageNodesired exam language
organizationNoorganization identification string to assign the exam to, only an organization of the API application owner can be used, always the organization of the user for organizational members
copy_settingsNooptional exam identification string to copy settings from
keep_certificate_settingsNowhether to keep certificate settings from the copied exam (default: false)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
examYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.0.0
    • removedOutput schema / properties / exam / description
      Removed value: -"exam identification string"
  2. Changed6 schema fields changedv1.2.15
    • removedInput schema / properties / close
      Removed value: -{
-  "description": "exam end time (in YYYY-MM-DD HH:ii:ss format)",
-  "type": "string"
-}
    • addedInput schema / properties / end
      Added value: +{
+  "description": "exam end time (in YYYY-MM-DD HH:ii:ss format)",
+  "type": "string"
+}
    • removedInput schema / properties / open
      Removed value: -{
-  "description": "exam start time (in YYYY-MM-DD HH:ii:ss format)",
-  "type": "string"
-}
    • addedInput schema / properties / organization
      Added value: +{
+  "description": "organization identification string to assign the exam to, only an organization of the API application owner can be used, always the organization of the user for organizational members",
+  "type": "string"
+}
    • addedInput schema / properties / start
      Added value: +{
+  "description": "exam start time (in YYYY-MM-DD HH:ii:ss format)",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "title",
-  "quiz",
-  "open",
-  "close"
-]New value: +[
+  "title",
+  "quiz",
+  "start",
+  "end"
+]
  3. Changed12 schema fields changedv1.1.2
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / close / description
      Previous value: -"exam end time (in YYYY-mm-dd HH:ii:ss format)"New value: +"exam end time (in YYYY-MM-DD HH:ii:ss format)"
    • addedInput schema / properties / copy_settings
      Added value: +{
+  "description": "optional exam identification string to copy settings from",
+  "type": "string"
+}
    • changedInput schema / properties / id / description
      Previous value: -"External unique exam identifier.\nShould be maximum 64 characters long!"New value: +"external unique exam identifier"
    • addedInput schema / properties / id / maxLength
      Added value: +64
    • addedInput schema / properties / id / minLength
      Added value: +1
    • addedInput schema / properties / keep_certificate_settings
      Added value: +{
+  "description": "whether to keep certificate settings from the copied exam (default: false)",
+  "type": "boolean"
+}
    • changedInput schema / properties / open / description
      Previous value: -"exam start time (in YYYY-mm-dd HH:ii:ss format)"New value: +"exam start time (in YYYY-MM-DD HH:ii:ss format)"
    • changedInput schema / properties / quiz / description
      Previous value: -"the Quiz set (specified using the quiz identification string) the exam is attached to"New value: +"the Quiz set (specified using the Quiz identification string) the exam is attached to"
    • changedInput schema / properties / type / description
      Previous value: -"Type of the exam. (default: exam)\n- exam: regular exam\n- championship: exam with championship features enabled\n- homework: homework assignment, can be paused and continued during the exam period\n- survey: survey (optionally anonymous) with no grading"New value: +"type of the exam (default: exam)"
    • addedInput schema / properties / type / enum
      Added value: +[
+  "exam",
+  "championship",
+  "homework",
+  "survey"
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "exam": {
+      "description": "exam identification string",
+      "type": "string"
+    }
+  },
+  "required": [
+    "exam"
+  ],
+  "type": "object"
+}
  4. First observedv1.0.22

TDQS

A4.1/5.0
Behavior4/5

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

Annotations indicate readOnlyHint=false, idempotentHint=false, and destructiveHint=false. The description adds context that exams are 'time-constrained, secured assessment instances', clarifying the behavioral nature of the created object. It does not fully disclose all side effects, but with annotations present, the description adds meaningful context without contradiction.

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 description is concise, two sentences, with the key constraint ('MUST be created from existing Quiz sets') placed early. It avoids repetition of the schema and annotations. It could be slightly more front-loaded about the prerequisite, but overall it is efficient.

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?

With 10 parameters and a complete output schema, the description is relatively complete for an agent to understand the core purpose and constraint. The description does not explain required versus optional parameters or edge cases, but the schema provides that. Given the tool's moderate complexity and the existing schema coverage, it is adequate.

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%, so the schema already documents each parameter. The description mentions the 'quiz' parameter must reference an existing Quiz set, which adds a bit of context beyond the schema but does not explain formats or optional behaviors like copy_settings. Given full schema coverage, a baseline of 3 is appropriate.

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 clearly states the action ('Create a new exam') and specifies the mandatory resource ('from an existing Quiz set'). It also defines key attributes of the exam (time-constrained, secured, top-level), which effectively distinguishes it from other exam-related tools like edubase_patch_exam or edubase_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 explicitly states that exams MUST be created from existing Quiz sets, providing a critical precondition. It also implies when not to use it (only for creating, not for editing or settings changes), but it does not explicitly name alternatives or list exclusions. However, in the context of a large sibling set, this guidance is sufficient.

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