Skip to main content
Glama
EduBase

EduBase MCP Server

Official
by EduBase
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

edubase_get_class

Read-onlyIdempotent

Retrieve class details from EduBase using a class identification string. Verify class existence and access class information for educational management tasks.

Instructions

Get/check class.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
classYesclass identification string

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoexternal unique class identifier (if set for the class)
endNoend date and time (if set)
classYesclass identification string
startNostart date and time (if set)
titleYestitle of the class

Schema Changelog

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

  1. Changed3 schema fields changedv1.2.15
    • removedOutput schema / properties / name
      Removed value: -{
-  "description": "title of the class",
-  "type": "string"
-}
    • addedOutput schema / properties / title
      Added value: +{
+  "description": "title of the class",
+  "type": "string"
+}
    • changedOutput schema / required
      Previous value: -[
-  "class",
-  "name"
-]New value: +[
+  "class",
+  "title"
+]
  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": {
+    "class": {
+      "description": "class identification string",
+      "type": "string"
+    },
+    "end": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "end date and time (if set)"
+    },
+    "id": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "external unique class identifier (if set for the class)"
+    },
+    "name": {
+      "description": "title of the class",
+      "type": "string"
+    },
+    "start": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "start date and time (if set)"
+    }
+  },
+  "required": [
+    "class",
+    "name"
+  ],
+  "type": "object"
+}
  3. First observedv1.0.22

TDQS

D1.9/5.0
Behavior2/5

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

Annotations already indicate readOnlyHint, idempotentHint, and destructiveHint=false. The description adds only the ambiguous 'Get/check', which neither clarifies a return format nor reveals whether it checks existence or retrieves full data—so it does not meaningfully go 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.

Conciseness2/5

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

The sentence is terse but under-specified. It does not contain enough content to be called appropriately structured; it is merely a placeholder-level phrase that does not convey necessary context.

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

Completeness1/5

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

Given the large set of class-related sibling tools and no explanation of the resource, the description is far from complete. The presence of an output schema does not make up for the absence of any functional or context-defining text; an agent cannot understand what data is affected or what results to expect beyond the bare phrase 'Get/check class'.

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% and already documents the 'class' parameter as a 'class identification string'. The description adds no further meaning to this parameter, so the schema carries the full explanatory burden; the baseline of 3 applies.

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 says 'Get/check class' but does not define what 'class' refers to in this domain or what 'check' implies. It essentially restates the resource name, so an agent cannot distinguish it from sibling tools like edubase_get_class_assignments or edubase_get_classes.

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?

The description provides no information about when to use this tool, what context favors it over alternatives, or any preconditions or exclusions. An agent has no guidance on how to choose between this and its many class-related siblings.

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