EduBase MCP Server

Official

by EduBase

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

edubase_get_organization_members

Read-onlyIdempotent

List organization members with their names, departments, and permission levels for access management.

Instructions

List the members of an organization, with their names, departments and permission levels (to the organization, its contents and its members).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`organization`	Yes	organization identification string

Output Schema

TableJSON Schema

Name	Required	Description	Default
`members`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedv2.0.0Sep 15, 2026
- removedOutput schema / properties / members / items / properties / department / description
```
Removed value: -"name of the department (if member)"
```
- removedOutput schema / properties / members / items / properties / name / description
```
Removed value: -"name of the member"
```
- removedOutput schema / properties / members / items / properties / permission / description
```
Removed value: -"permissions"
```
- removedOutput schema / properties / members / items / properties / permission / properties / content / description
```
Removed value: -"permission level to contents in organization"
```
- removedOutput schema / properties / members / items / properties / permission / properties / members / description
```
Removed value: -"permission level to members in organization"
```
- removedOutput schema / properties / members / items / properties / permission / properties / organization / description
```
Removed value: -"permission level to organization"
```
- removedOutput schema / properties / members / items / properties / user / description
```
Removed value: -"user identification string"
```
Changed2 schema fields changedv1.2.9Aug 18, 2026
- addedOutput schema / properties / members / items / properties / permission / properties / members
```
Added value: +{
+  "description": "permission level to members in organization",
+  "type": "string"
+}
```
- changedOutput schema / properties / members / items / properties / permission / required
```
Previous value: -[
-  "organization",
-  "content"
-]New value: +[
+  "organization",
+  "content",
+  "members"
+]
```

Changed2 schema fields changedv1.1.2Mar 13, 2026

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": {
+          "department": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "name of the department (if member)"
+          },
+          "name": {
+            "description": "name of the member",
+            "type": "string"
+          },
+          "permission": {
+            "additionalProperties": false,
+            "description": "permissions",
+            "properties": {
+              "content": {
+                "description": "permission level to contents in organization",
+                "type": "string"
+              },
+              "organization": {
+                "description": "permission level to organization",
+                "type": "string"
+              }
+            },
+            "required": [
+              "organization",
+              "content"
+            ],
+            "type": "object"
+          },
+          "user": {
+            "description": "user identification string",
+            "type": "string"
+          }
+        },
+        "required": [
+          "user",
+          "name",
+          "permission"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "members"
+  ],
+  "type": "object"
+}

First observedv1.0.22Feb 21, 2026

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 and destructiveHint=false, so the safety profile is covered. The description adds context about the returned data (names, departments, permission levels), which is beyond the schema. No contradictions, and it appropriately supplements 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?

The description is a single sentence that is concise and front-loaded with the primary action. It avoids unnecessary words and clearly communicates the tool's purpose and output.

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?

Given the tool's simplicity (one parameter, read-only, with output schema), the description is complete. It states what the tool does and what information is returned. No additional context is needed for correct invocation.

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 schema fully describes the single parameter 'organization' with a description 'organization identification string'. The description does not add additional parameter details, but with 100% 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 uses a specific verb 'List' and resource 'members of an organization', and specifies the returned fields (names, departments, permission levels). This clearly distinguishes it from sibling tools like edubase_get_organization_departments or edubase_get_organization.

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 implies usage when you need member information for an organization. It does not explicitly mention alternatives or exclusions, but the context is clear enough to differentiate from related tools like get_organization_departments or get_organization_competencies. No explicit guidance on when not to use, but the purpose is unambiguous.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server