Skip to main content
Glama
EduBase

EduBase MCP Server

Official
by EduBase
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

edubase_get_exam

Read-onlyIdempotent

Retrieve detailed exam information by exam identification. Use this tool to check exam status and access exam data from the EduBase platform.

Instructions

Get/check exam.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
examYesexam identification string

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoexternal unique exam identifier (if set for the exam)
endYesend date and time
examYesexam identification string
quizYesQuiz identification string. The Quiz set the exam is attached to
startYesstart date and time
titleYestitle of the exam
activeYesexam is active
secureYesexam can only be started with the Safe Exam Browser
statusYesexam status (INACTIVE, ACTIVE, PAUSED, REVIEW, EXPIRED)
deadlineNolatest date and time the exam can be started at (if set for the exam)
languageYeslanguage of the exam
descriptionNodescription of the exam (only present if set for the exam)
seb_config_urlNoSafe Exam Browser configuration file URL (only present if secure is true)
seb_launch_urlNoSafe Exam Browser launch URL (only present if secure is true)

Schema Changelog

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

  1. Changed9 schema fields changedv1.2.15
    • 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"
+]
  2. Changed2 schema fields changedv1.1.2
    • 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"
+}
  3. First observedv1.0.22

TDQS

C2.1/5.0
Behavior2/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 established. However, the description adds no behavioral context about what 'check' entails (e.g., does it return a full exam object or just a status?), and thus provides little value beyond 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.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is one short phrase with no filler, but it is so terse that it borders on under-specification. It is concise but lacks the structure needed to convey the tool's actual function clearly.

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

Completeness2/5

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

With a single required parameter and an output schema present, the basic mechanics are simple. However, the description fails to provide essential context for agent decision-making, such as whether this retrieves an exam or checks existence, and how it differs from edubase_get_exams. The completeness is inadequate given the complex sibling landscape.

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?

The input schema covers 100% of the parameter description ('exam identification string'), so the schema carries the semantic weight. The tool description does not add any additional meaning or format details, placing it at the baseline for high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses the verb 'Get' and the resource 'exam', but the addition of 'check' introduces ambiguity: it could mean retrieving full details or merely verifying existence. It also does not differentiate from siblings like edubase_get_exams or edubase_get_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 Guidelines1/5

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

No guidance is given about when to use this tool versus alternatives. The description does not mention any distinguishing context, leaving the agent to guess among dozens of exam-related sibling tools.

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