Skip to main content
Glama
EduBase

EduBase MCP Server

Official
by EduBase
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

edubase_get_organizations

Read-onlyIdempotent

List owned and managed organizations with IDs, external identifiers, and titles. Filter by search or paginate results.

Instructions

List owned and managed organizations. Returns organization identification strings, external identifiers and titles.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNopage number (default: 1), not used in search mode!
limitNolimit number of results (default: 16)
searchNosearch string to filter results

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
organizationsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.0.0
    • 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 / organization / description
      Removed value: -"organization identification string"
    • removedOutput schema / properties / organizations / items / properties / title / description
      Removed value: -"title of the organization"
  2. Changed3 schema fields changedv1.2.15
    • 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"
-]New value: +[
+  "organization",
+  "title"
+]
  3. Addedv1.2.9
  4. Removedv1.2.8
  5. Changed9 schema fields changedv1.1.2
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / properties / limit / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / limit / minimum
      Added value: +-9007199254740991
    • changedInput schema / properties / limit / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / page / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / page / minimum
      Added value: +-9007199254740991
    • changedInput schema / properties / page / type
      Previous value: -"number"New value: +"integer"
    • removedInput schema / required
      Removed value: -[]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "organizations": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "id": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "external unique organization identifier (if set for the organization)"
+          },
+          "name": {
+            "description": "title of the organization",
+            "type": "string"
+          },
+          "organization": {
+            "description": "organization identification string",
+            "type": "string"
+          }
+        },
+        "required": [
+          "organization",
+          "name"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "organizations"
+  ],
+  "type": "object"
+}
  6. First observedv1.0.22

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior, so the safety profile is clear. The description adds the return contents and scope, but does not discuss pagination behavior beyond what the parameter schema already documents.

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 short, direct sentences communicate scope and return value with no filler. The most important information is front-loaded in the first sentence.

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?

For a read-only list tool with fully documented optional parameters and an output schema, the description is nearly complete. The only noticeable gap is the lack of explicit sibling differentiation, but this is partly covered by the plural scope in the description.

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 description coverage is 100%, so the parameter meanings are fully documented in the input schema. The tool description does not add further parameter-level detail, which is acceptable at the baseline level.

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 starts with a specific verb ('List') and a clear resource ('owned and managed organizations'), and it states what is returned (identification strings, external identifiers, titles). This clearly distinguishes it from singular tools like edubase_get_organization or membership-focused tools like edubase_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 Guidelines3/5

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

The scope 'owned and managed organizations' implies this is for enumerating organizations the caller controls, but the description does not explicitly contrast it with alternatives such as edubase_get_user_organizations or edubase_get_organization. There is no when-not-to-use guidance.

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