EduBase MCP Server

Official

by EduBase

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

edubase_get_user_organizations

Read-onlyIdempotent

Retrieve all organizations a user belongs to, including titles, links, department, and permission levels.

Instructions

List the organizations a user is member of, with their titles, links, the department of the user and the permission levels.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`user`	Yes	user identification string

Output Schema

TableJSON Schema

Name	Required	Description	Default
`organizations`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedv2.0.0Sep 15, 2026
- removedOutput schema / properties / organizations / items / properties / department / description
```
Removed value: -"name of the department (if member)"
```
- removedOutput schema / properties / organizations / items / properties / id / description
```
Removed value: -"external unique organization identifier (if set for the organization)"
```
- removedOutput schema / properties / organizations / items / properties / link / description
```
Removed value: -"link to the organization manager page"
```
- removedOutput schema / properties / organizations / items / properties / organization / description
```
Removed value: -"organization identification string"
```
- removedOutput schema / properties / organizations / items / properties / permission / description
```
Removed value: -"permissions"
```
- removedOutput schema / properties / organizations / items / properties / permission / properties / content / description
```
Removed value: -"permission level to contents in organization"
```
- removedOutput schema / properties / organizations / items / properties / permission / properties / members / description
```
Removed value: -"permission level to members in organization"
```
- removedOutput schema / properties / organizations / items / properties / permission / properties / organization / description
```
Removed value: -"permission level to organization"
```
- removedOutput schema / properties / organizations / items / properties / title / description
```
Removed value: -"title of the organization"
```

Changed3 schema fields changedv1.2.15Sep 2, 2026

removedOutput schema / properties / organizations / items / properties / name

Removed value: -{
-  "description": "title of the organization",
-  "type": "string"
-}

addedOutput schema / properties / organizations / items / properties / title

Added value: +{
+  "description": "title of the organization",
+  "type": "string"
+}

changedOutput schema / properties / organizations / items / required

Previous value: -[
-  "organization",
-  "name",
-  "link",
-  "permission"
-]New value: +[
+  "organization",
+  "title",
+  "link",
+  "permission"
+]

Addedv1.2.9Aug 18, 2026
Removedv1.2.8Jul 17, 2026

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": {
+    "organizations": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "department": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "name of the department (if member)"
+          },
+          "id": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "external unique organization identifier (if set for the organization)"
+          },
+          "link": {
+            "description": "link to the organization manager page",
+            "type": "string"
+          },
+          "name": {
+            "description": "title of the organization",
+            "type": "string"
+          },
+          "organization": {
+            "description": "organization identification string",
+            "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"
+          }
+        },
+        "required": [
+          "organization",
+          "name",
+          "link",
+          "permission"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "organizations"
+  ],
+  "type": "object"
+}

First observedv1.0.22Feb 21, 2026

TDQS

A3.7/5.0

Behavior3/5

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

The description is consistent with the annotations: readOnlyHint=true, idempotentHint=true, and destructiveHint=false, and 'List' accurately reflects a read operation. However, it adds no behavioral context beyond the annotations, such as pagination, auth requirements, or scope caveats.

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, front-loaded sentence that states the action and resource immediately, then lists the relevant result fields. There is no filler or redundant information.

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 lookup with one documented parameter, full annotation coverage, and an output schema present. The description conveys what the tool returns, which is sufficient for an agent to select and invoke it correctly.

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 input schema fully documents the single required 'user' parameter with 100% coverage, including 'user identification string'. The description adds no additional meaning beyond what the schema already provides, so the baseline score 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 uses a specific verb ('List') and resource ('organizations a user is member of'), then enumerates the returned fields: titles, links, department, and permission levels. This clearly distinguishes it from siblings like get_user_classes, get_organizations, and get_organization_members.

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?

There is no explicit guidance on when to use this tool versus alternatives such as get_user_classes or get_organization_members. The intended use is implied by the name and description, but no exclusions or alternative routing are provided.

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

Deploy Server