EduBase MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

edubase_get_organization_members

Read-onlyIdempotent

List organization members with names, departments, job roles, permission levels, and management restrictions for access review and administration.

Instructions

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

Input Schema

Name	Required	Description	Default
`organization`	Yes	organization identification string

Output Schema

Name	Required	Description	Default
`members`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv2.0.9Oct 26, 2026

addedOutput schema / properties / members / items / properties / job

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

addedOutput schema / properties / members / items / properties / permission / properties / custom
```
Added value: +{
+  "type": "boolean"
+}
```

changedOutput schema / properties / members / items / properties / permission / required

Previous value: -[
-  "organization",
-  "content",
-  "members"
-]New value: +[
+  "organization",
+  "content",
+  "members",
+  "custom"
+]

addedOutput schema / properties / members / items / properties / restriction

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "competencies": {
+      "type": "boolean"
+    },
+    "library": {
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}

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

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description's added value is disclosing that sensitive fields (permission levels over the organization, its contents and its members, plus management restrictions) are returned, but it says nothing about pagination, volume, or auth requirements.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

One front-loaded sentence with no filler; the core action comes first and the return payload is enumerated after. It is essentially a single clustered noun phrase, though nothing is wasted.

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?

With an output schema present and rich annotations, the description need not explain return structure, and it correctly focuses on the resource and the notable data surfaced. Only behavioral caveats about listing an org's membership at scale are 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?

There is a single required parameter with 100% schema description coverage ('organization identification string'), so the schema already carries the burden. The description adds no extra semantics such as accepted identifier formats (ID vs slug vs name), which is the one place it could have helped.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('List') and resource ('members of an organization') and enumerates the member attributes returned, so an agent knows exactly what it retrieves. It does not explicitly distinguish itself from the sibling write/delete variants (post_organization_members, delete_organization_members), relying on the name prefix instead.

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?

Usage is only implied: the agent can infer this is the read path for organization membership data. There is no statement of when to prefer it over alternatives, no prerequisites (e.g., required org-level permissions), and no note about result size or ordering.

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

Deploy Server