Skip to main content
Glama
EduBase

EduBase MCP Server

Official
by EduBase
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

edubase_get_classes

Read-onlyIdempotent

List owned and managed classes to retrieve their IDs, external identifiers, and titles. Supports search filtering and pagination.

Instructions

List owned and managed classes. Returns class identification strings, external identifiers and titles.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNopage number (default: 1), not used in search mode!
limitNolimit number of results (default: 16)
searchNosearch string to filter results

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
classesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.0.0
    • removedOutput schema / properties / classes / items / properties / class / description
      Removed value: -"class identification string"
    • removedOutput schema / properties / classes / items / properties / id / description
      Removed value: -"external unique class identifier (if set for the class)"
    • removedOutput schema / properties / classes / items / properties / title / description
      Removed value: -"title of the class"
  2. Changed3 schema fields changedv1.2.15
    • removedOutput schema / properties / classes / items / properties / name
      Removed value: -{
-  "description": "title of the class",
-  "type": "string"
-}
    • addedOutput schema / properties / classes / items / properties / title
      Added value: +{
+  "description": "title of the class",
+  "type": "string"
+}
    • changedOutput schema / properties / classes / items / required
      Previous value: -[
-  "class",
-  "name"
-]New value: +[
+  "class",
+  "title"
+]
  3. Changed9 schema fields changedv1.1.2
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • 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": {
+    "classes": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "class": {
+            "description": "class identification string",
+            "type": "string"
+          },
+          "id": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "external unique class identifier (if set for the class)"
+          },
+          "name": {
+            "description": "title of the class",
+            "type": "string"
+          }
+        },
+        "required": [
+          "class",
+          "name"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "classes"
+  ],
+  "type": "object"
+}
  4. First observedv1.0.22

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, openWorld, and non-destructive behavior. The description adds value by stating the exact shape of the response (identification strings, external identifiers, titles), which is behavior not captured by the annotations. No contradictions with annotations were found.

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 filler. The primary action is front-loaded, and the output details are provided in a single follow-up sentence. Every word serves a purpose.

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?

This is a simple read-only list operation with three optional parameters, all documented in the schema, and an output schema is available. The annotations cover safety and idempotency. The description provides enough context about scope and return values, so nothing essential is missing for an agent to invoke it 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?

The input schema documents all three parameters (page, limit, search) with descriptions, so schema coverage is 100%. The tool description adds no extra parameter-level guidance, which is acceptable given that the schema carries the full burden. This is a baseline score as the description does not need to compensate for schema gaps.

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 and resource ('List owned and managed classes') and clarifies the output ('class identification strings, external identifiers and titles'). This distinguishes it from sibling tools like edubase_get_class or edubase_get_user_classes by specifying the ownership/managed scope.

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

Usage Guidelines4/5

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

The description clearly conveys when to use this tool: to list classes the caller owns or manages. It does not explicitly name alternatives or exclusion conditions, but the resource scope provides sufficient context for selecting it over related class-listing 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