Skip to main content
Glama
EduBase

EduBase MCP Server

Official
by EduBase
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

edubase_get_class_members

Read-onlyIdempotent

Retrieve class members with their names and active membership status to verify approved, non-expired participation.

Instructions

List the members of a class, with their names and whether their membership is active (approved and not expired).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
classYesclass identification string

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
membersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.0.0
    • removedOutput schema / properties / members / items / properties / active / description
      Removed value: -"active membership (approved and not expired)"
    • removedOutput schema / properties / members / items / properties / name / description
      Removed value: -"name of the member"
    • removedOutput schema / properties / members / items / properties / user / description
      Removed value: -"user identification string"
  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": {
+    "members": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "active": {
+            "description": "active membership (approved and not expired)",
+            "type": "boolean"
+          },
+          "name": {
+            "description": "name of the member",
+            "type": "string"
+          },
+          "user": {
+            "description": "user identification string",
+            "type": "string"
+          }
+        },
+        "required": [
+          "user",
+          "name",
+          "active"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "members"
+  ],
+  "type": "object"
+}
  3. First observedv1.0.22

TDQS

A3.8/5.0
Behavior4/5

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

The description clarifies that 'active' means 'approved and not expired', adding semantic meaning beyond the readOnlyHint annotation. It also implicitly confirms a safe read operation consistent with the annotations, though it does not describe pagination or result shape (output schema exists).

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, focused sentence with no wasted words. It state the action, resource, and output clearly, making it easy for an agent to parse quickly.

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

Completeness4/5

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

Given a single parameter and an output schema, the description covers the key behavior (listing members with names and active status) and defines a term ('active') that could be ambiguous. It doesn't describe error handling or edge cases, but those are not typically required when an output schema exists.

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 coverage is 100% but the parameter description 'class identification string' is minimal. The tool description does not elaborate on the parameter's format or source (e.g., 'use the ID from get_classes'). Therefore, it meets the baseline but adds no extra meaning beyond the schema.

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 explicitly states the action (list), the resource (members of a class), and the output (names and whether membership is active). It is unambiguous and distinguishes this tool as a read operation for class members, not confused with other class-related tools.

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

Usage Guidelines2/5

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

The description gives no guidance on when to use this tool over its many sibling tools (e.g., edubase_get_class, edubase_get_user_classes, edubase_get_class_assignments). It does not mention alternative tools or conditions, leaving the agent to infer usage from the tool name alone.

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