Skip to main content
Glama
EduBase

EduBase MCP Server

Official
by EduBase
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

edubase_post_exam

Create a new exam from an existing Quiz set, scheduling its start and end times for secured, time-constrained assessments.

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
examYesexam identification string

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 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"
+]
  2. 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"
+}
  3. First observedv1.0.22

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already cover the read/write/destructive profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false). The description adds contextual traits like 'time-constrained' and 'secured', but does not disclose additional behavioral details such as side effects, permission requirements, or post-creation processes. It neither contradicts annotations nor richly expands beyond them.

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?

Three sentences, no wasted words. The core action is front-loaded, and the critical constraint (must come from existing Quiz set) is explicitly highlighted in the second sentence. Very efficient for the amount of context provided.

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?

The description is sufficient given the rich schema (all params documented) and presence of an output schema. It clearly explains the prerequisite and the nature of exams. Minor gap: it does not clarify the relationship to sibling settings operations, but that is not essential for invoking the tool correctly.

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?

All parameters are already documented in the input schema with descriptions (100% coverage). The tool description adds no new parameter-specific meaning beyond restating the 'quiz' prerequisite. Baseline 3 is appropriate because the schema carries the semantic weight.

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 verb (create), the resource (a new exam), and the key constraint (from an existing Quiz set). It also distinguishes this tool from sibling exam-related operations by emphasizing the top-level hierarchy and that exams are instances of Quiz sets, which is unique to the creation action.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the primary use case—creating an exam—and states a prerequisite (must use an existing Quiz set). However, it does not explicitly say when to use this tool versus related operations like patch_exam or post_exam_settings, nor does it mention alternatives or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/EduBase/MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server