Skip to main content
Glama
EduBase

EduBase MCP Server

Official
by EduBase
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

edubase_get_exam_users

Read-onlyIdempotent

List all users assigned to an exam with their names. Use this to check which participants are registered for a specific exam.

Instructions

List the users assigned to an exam, with their names. Assign users with edubase_post_exam_users.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
examYesexam identification string

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
usersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.0.0
    • removedOutput schema / properties / users / items / properties / name / description
      Removed value: -"name of the examinee"
    • removedOutput schema / properties / users / 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": {
+    "users": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "name": {
+            "description": "name of the examinee",
+            "type": "string"
+          },
+          "user": {
+            "description": "user identification string",
+            "type": "string"
+          }
+        },
+        "required": [
+          "user",
+          "name"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "users"
+  ],
+  "type": "object"
+}
  3. 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 declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds that the output includes user names and routes mutation needs to the post endpoint, which is useful behavioral context 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.

Conciseness5/5

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

Two concise sentences with no filler. The core purpose is stated first, and the second sentence efficiently points to the complementary write tool 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?

This is a simple read-only listing tool with one fully documented parameter, an output schema, and safety annotations. The description gives sufficient orientation, including the relationship to the assignment endpoint, so nothing essential 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?

The single required parameter 'exam' has full schema coverage with a clear description ('exam identification string'). The tool description's phrase 'assigned to an exam' reinforces the parameter's role but does not add new format or constraint details, so the baseline of 3 applies.

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') and resource ('users assigned to an exam'), and clarifies that names are included. It also implicitly distinguishes itself from sibling tools like edubase_post_exam_users by naming that tool for the assignment operation.

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 explicitly points to edubase_post_exam_users for assigning users, which makes clear that this tool is for the read-only listing case. It provides useful context but does not spell out all exclusions or alternative read tools such as edubase_get_exam.

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