Skip to main content
Glama
EduBase

EduBase MCP Server

Official
by EduBase
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

edubase_get_organization

Read-onlyIdempotent

Retrieve organization details from EduBase, including title, external identifier, and description, by providing the organization identification string.

Instructions

Get the details of an organization: title, external identifier and description.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
organizationYesorganization identification string

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
titleYes
descriptionNo
organizationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.0.0
    • removedOutput schema / properties / description / description
      Removed value: -"short description of the organization (only present if set for the organization)"
    • removedOutput schema / properties / id / description
      Removed value: -"external unique organization identifier (if set for the organization)"
    • removedOutput schema / properties / organization / description
      Removed value: -"organization identification string"
    • removedOutput schema / properties / title / description
      Removed value: -"title of the organization"
  2. Changed4 schema fields changedv1.2.15
    • addedOutput schema / properties / description
      Added value: +{
+  "description": "short description of the organization (only present if set for the organization)",
+  "type": "string"
+}
    • removedOutput schema / properties / name
      Removed value: -{
-  "description": "title of the organization",
-  "type": "string"
-}
    • addedOutput schema / properties / title
      Added value: +{
+  "description": "title of the organization",
+  "type": "string"
+}
    • changedOutput schema / required
      Previous value: -[
-  "organization",
-  "name"
-]New value: +[
+  "organization",
+  "title"
+]
  3. Addedv1.2.9
  4. Removedv1.2.8
  5. 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": {
+    "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"
+}
  6. First observedv1.0.22

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the specific fields returned (title, external identifier, description), which is useful but does not disclose behavior like error cases, required permissions, or whether the organization identifier is an ID or slug. No contradiction with annotations.

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?

The description is a single, front-loaded sentence that states the action and the returned fields with no filler. It is concise and easy to scan, though it could have added a usage hint without becoming verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple single-parameter read tool with an output schema and strong annotations, the description is mostly adequate. However, it does not clarify what the 'organization' parameter should be (ID vs. external identifier) or how this differs from the plural list endpoint, which are minor gaps for an agent selecting among many organization-related siblings.

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%: the only parameter 'organization' is described as 'organization identification string'. The description adds no further meaning about what format the identification string takes (e.g., UUID vs. external identifier), so it does not go beyond the schema. Baseline 3 is appropriate.

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?

The description states a specific verb ('Get') and resource ('organization details'), and lists the returned fields (title, external identifier, description). It is clear and distinguishes from siblings like edubase_get_organizations (plural) and edubase_get_organization_members, though it doesn't explicitly name them.

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 description implies a read operation for fetching a single organization's details, and the readOnlyHint annotation reinforces when it is appropriate. However, it does not explicitly state when to use this over edubase_get_organizations (list) or edubase_get_organization_competencies, leaving the agent to infer from the resource name.

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