EduBase MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

edubase_get_exam

Read-onlyIdempotent

Retrieve exam details including title, language, quiz set, status, active state, start/end times, deadline, and Safe Exam Browser links.

Instructions

Get the details of an exam: title, language, the Quiz set it uses, active state, status (INACTIVE, ACTIVE, PAUSED, REVIEW, EXPIRED), start and end times, deadline and Safe Exam Browser links. Use edubase_get_exam_settings for its settings.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`exam`	Yes	exam identification string

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	No
`end`	Yes
`exam`	Yes
`quiz`	Yes
`start`	Yes
`title`	Yes
`active`	Yes
`secure`	Yes
`status`	Yes
`deadline`	No
`language`	Yes
`description`	No
`seb_config_url`	No
`seb_launch_url`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed14 schema fields changedv2.0.0Sep 15, 2026

removedOutput schema / properties / active / description
```
Removed value: -"exam is active"
```

removedOutput schema / properties / deadline / description

Removed value: -"latest date and time the exam can be started at (if set for the exam)"

removedOutput schema / properties / description / description

Removed value: -"description of the exam (only present if set for the exam)"

removedOutput schema / properties / end / description
```
Removed value: -"end date and time"
```
removedOutput schema / properties / exam / description
```
Removed value: -"exam identification string"
```

removedOutput schema / properties / id / description

Removed value: -"external unique exam identifier (if set for the exam)"

removedOutput schema / properties / language / description
```
Removed value: -"language of the exam"
```

removedOutput schema / properties / quiz / description

Removed value: -"Quiz identification string. The Quiz set the exam is attached to"

removedOutput schema / properties / seb_config_url / description

Removed value: -"Safe Exam Browser configuration file URL (only present if secure is true)"

removedOutput schema / properties / seb_launch_url / description

Removed value: -"Safe Exam Browser launch URL (only present if secure is true)"

removedOutput schema / properties / secure / description

Removed value: -"exam can only be started with the Safe Exam Browser"

removedOutput schema / properties / start / description
```
Removed value: -"start date and time"
```

removedOutput schema / properties / status / description

Removed value: -"exam status (INACTIVE, ACTIVE, PAUSED, REVIEW, EXPIRED)"

removedOutput schema / properties / title / description
```
Removed value: -"title of the exam"
```

Changed9 schema fields changedv1.2.15Sep 2, 2026

addedOutput schema / properties / deadline

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "latest date and time the exam can be started at (if set for the exam)"
+}

addedOutput schema / properties / description

Added value: +{
+  "description": "description of the exam (only present if set for the exam)",
+  "type": "string"
+}

addedOutput schema / properties / language

Added value: +{
+  "description": "language of the exam",
+  "type": "string"
+}

removedOutput schema / properties / name

Removed value: -{
-  "description": "title of the exam",
-  "type": "string"
-}

addedOutput schema / properties / seb_config_url

Added value: +{
+  "description": "Safe Exam Browser configuration file URL (only present if secure is true)",
+  "format": "uri",
+  "type": "string"
+}

addedOutput schema / properties / seb_launch_url

Added value: +{
+  "description": "Safe Exam Browser launch URL (only present if secure is true)",
+  "format": "uri",
+  "type": "string"
+}

addedOutput schema / properties / secure

Added value: +{
+  "description": "exam can only be started with the Safe Exam Browser",
+  "type": "boolean"
+}

addedOutput schema / properties / title

Added value: +{
+  "description": "title of the exam",
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "exam",
-  "name",
-  "quiz",
-  "active",
-  "status",
-  "start",
-  "end"
-]New value: +[
+  "exam",
+  "title",
+  "language",
+  "quiz",
+  "active",
+  "status",
+  "secure",
+  "start",
+  "end"
+]

Changed2 schema fields changedv1.1.2Mar 13, 2026

addedInput schema / $schema

Added value: +"http://json-schema.org/draft-07/schema#"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "active": {
+      "description": "exam is active",
+      "type": "boolean"
+    },
+    "end": {
+      "description": "end date and time",
+      "type": "string"
+    },
+    "exam": {
+      "description": "exam identification string",
+      "type": "string"
+    },
+    "id": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "external unique exam identifier (if set for the exam)"
+    },
+    "name": {
+      "description": "title of the exam",
+      "type": "string"
+    },
+    "quiz": {
+      "description": "Quiz identification string. The Quiz set the exam is attached to",
+      "type": "string"
+    },
+    "start": {
+      "description": "start date and time",
+      "type": "string"
+    },
+    "status": {
+      "description": "exam status (INACTIVE, ACTIVE, PAUSED, REVIEW, EXPIRED)",
+      "enum": [
+        "INACTIVE",
+        "ACTIVE",
+        "PAUSED",
+        "REVIEW",
+        "EXPIRED"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "exam",
+    "name",
+    "quiz",
+    "active",
+    "status",
+    "start",
+    "end"
+  ],
+  "type": "object"
+}

First observedv1.0.22Feb 21, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered. The description adds behavioral context beyond that by enumerating the payload contents and clarifying that settings are excluded from this call, setting accurate expectations about what the agent will receive.

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?

Two sentences with zero waste: the first delivers the core purpose and payload list, the second routes to the relevant sibling. No redundancy with the annotations or schema; every sentence earns its 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?

The tool is a simple 1-param read operation with rich annotations, full schema coverage, and an output schema that documents return values. The description covers purpose, scope, and the key sibling distinction; nothing an agent needs to invoke it correctly is missing.

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% — the single 'exam' parameter is documented as 'exam identification string'. The description adds no additional parameter guidance (e.g., whether the string is an ID, slug, or UUID), so with full schema coverage the baseline of 3 applies.

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?

States a specific verb ('Get') and resource (details of an exam) and enumerates the exact returned fields: title, language, quiz set, active state, status, times, deadline, and Safe Exam Browser links. It also distinguishes itself from the confusable sibling edubase_get_exam_settings, which is critical given the large sibling list.

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

Usage Guidelines5/5

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

Explicitly routes the agent to edubase_get_exam_settings when settings are needed, providing both an alternative and the condition that selects it. This resolves the most likely source of confusion among the many exam-related tools without leaving anything to inference.

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

Deploy Server