Skip to main content
Glama
EduBase

EduBase MCP Server

Official
by EduBase
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

edubase_get_user_classes

Read-onlyIdempotent

Retrieve all classes a user belongs to, including titles, links, and membership status. Quickly identify active and inactive memberships to manage educational access.

Instructions

List the classes a user is member of, with their titles, links and whether the membership is active.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
userYesuser identification string

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
classesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv2.0.0
    • removedOutput schema / properties / classes / items / properties / active / description
      Removed value: -"active membership (approved and not expired)"
    • 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 / link / description
      Removed value: -"link to the class page"
    • 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",
-  "link",
-  "active"
-]New value: +[
+  "class",
+  "title",
+  "link",
+  "active"
+]
  3. 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": {
+    "classes": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "active": {
+            "description": "active membership (approved and not expired)",
+            "type": "boolean"
+          },
+          "class": {
+            "description": "class identification string",
+            "type": "string"
+          },
+          "id": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "external unique class identifier (if set for the class)"
+          },
+          "link": {
+            "description": "link to the class page",
+            "type": "string"
+          },
+          "name": {
+            "description": "title of the class",
+            "type": "string"
+          }
+        },
+        "required": [
+          "class",
+          "name",
+          "link",
+          "active"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "classes"
+  ],
+  "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, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is fully covered. The description adds minor context about membership-active status but does not disclose other behavioral traits like ordering, pagination, or error behavior; this is acceptable given the annotation coverage.

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 a single, direct sentence that front-loads the core action and result contents. There is no redundant phrasing or filler.

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 one-parameter, read-only list operation with full schema coverage, an output schema, and rich annotations, the description is complete. Nothing needed to invoke the tool 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% and the single 'user' parameter is documented as a 'user identification string'. The description does not add extra parameter guidance, but with full schema coverage the baseline of 3 is appropriate.

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 states a specific verb ('List'), a specific resource ('classes a user is member of'), and the included fields ('titles, links and whether the membership is active'). This clearly distinguishes the tool from siblings like get_classes or get_user_classes-related write operations.

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 implies the use case: retrieving class memberships for a given user. However, it does not explicitly state when to prefer this tool over alternatives such as get_classes or get_class_members, nor does it mention any exclusions.

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