Skip to main content
Glama
EduBase

EduBase MCP Server

Official
by EduBase
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

edubase_get_exams

Read-onlyIdempotent

List exams from your EduBase account with optional filters for active status, search term, pagination, and result limit.

Instructions

List owned and managed exams. Exams are the highest level in the EduBase Quiz hierarchy, built from Quiz sets.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNopage number (default: 1), not used in search mode!
limitNolimit number of results (default: 16)
activeNooptional filter to only include active exams (if true) or inactive exams (if false)
searchNosearch string to filter results

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
examsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.0.0
    • removedOutput schema / properties / exams / items / properties / active / description
      Removed value: -"exam is active"
    • removedOutput schema / properties / exams / items / properties / exam / description
      Removed value: -"exam identification string"
    • removedOutput schema / properties / exams / items / properties / id / description
      Removed value: -"external unique exam identifier (if set for the exam)"
    • removedOutput schema / properties / exams / items / properties / title / description
      Removed value: -"title of the exam"
  2. Changed3 schema fields changedv1.2.15
    • removedOutput schema / properties / exams / items / properties / name
      Removed value: -{
-  "description": "title of the exam",
-  "type": "string"
-}
    • addedOutput schema / properties / exams / items / properties / title
      Added value: +{
+  "description": "title of the exam",
+  "type": "string"
+}
    • changedOutput schema / properties / exams / items / required
      Previous value: -[
-  "exam",
-  "name",
-  "active"
-]New value: +[
+  "exam",
+  "title",
+  "active"
+]
  3. Changed10 schema fields changedv1.1.2
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / properties / active
      Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "optional filter to only include active exams (if true) or inactive exams (if false)"
+}
    • addedInput schema / properties / limit / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / limit / minimum
      Added value: +-9007199254740991
    • changedInput schema / properties / limit / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / page / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / page / minimum
      Added value: +-9007199254740991
    • changedInput schema / properties / page / type
      Previous value: -"number"New value: +"integer"
    • removedInput schema / required
      Removed value: -[]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "exams": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "active": {
+            "description": "exam is active",
+            "type": "boolean"
+          },
+          "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"
+          }
+        },
+        "required": [
+          "exam",
+          "name",
+          "active"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "exams"
+  ],
+  "type": "object"
+}
  4. First observedv1.0.22

TDQS

A3.9/5.0
Behavior3/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 no contradiction exists. The description adds useful domain context about the exam hierarchy but does not disclose additional behavioral traits such as pagination behavior, ordering, or what the response contains. Given the annotations cover the safety profile, a mid-range score is appropriate.

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 two short sentences with no wasted words. The primary action is front-loaded ('List owned and managed exams'), and the second sentence provides relevant domain context without redundancy.

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?

For a simple read-only list endpoint, the description combined with the fully documented input schema, annotations, and presence of an output schema is sufficient. Nothing critical is missing for an agent to select and call this 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?

Schema description coverage is 100%, so the schema already documents all four parameters (page, limit, active, search) clearly. The description adds no additional parameter semantics beyond the schema, placing it at the baseline for fully documented schemas.

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 uses a specific verb ('List'), a resource ('owned and managed exams'), and differentiates from singular operations like edubase_get_exam by clearly indicating a plural list scope. The additional hierarchical context ('highest level in the EduBase Quiz hierarchy, built from Quiz sets') further clarifies what an exam is relative to other resources.

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 states the tool's purpose but does not explicitly say when to prefer this over alternatives such as edubase_get_exam (for a single exam) or edubase_get_quizes (for quiz sets). The intended use is implied rather than explicitly contrasted with sibling tools.

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