Skip to main content
Glama
EduBase

EduBase MCP Server

Official
by EduBase
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

edubase_get_organization

Read-onlyIdempotent

Fetch and verify organization details by providing the organization identification string. Get the organization's data to confirm its existence and access relevant information.

Instructions

Get/check organization.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
organizationYesorganization identification string

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoexternal unique organization identifier (if set for the organization)
titleYestitle of the organization
descriptionNoshort description of the organization (only present if set for the organization)
organizationYesorganization identification string

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 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"
+]
  2. Addedv1.2.9
  3. Removedv1.2.8
  4. 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"
+}
  5. First observedv1.0.22

TDQS

B3/5.0
Behavior3/5

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

Annotations (readOnlyHint=true, idempotentHint=true, destructiveHint=false) already communicate safety and side effects. The description adds no additional behavioral context, such as error behavior or how 'check' differs from a plain get. There is no contradiction with annotations, so a neutral 3 is appropriate.

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 concise sentence with no filler. Every word contributes to the basic purpose, and it is appropriately sized for a simple single-parameter tool.

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?

While the output schema and annotations cover return behavior and safety, the description lacks sufficient context to fully orient an agent: it doesn't clarify whether this is for fetching full organization details or merely checking existence, nor how it relates to the plural get_organizations. For such a simple tool, this is a notable gap in contextual guidance.

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 sole parameter 'organization' is fully described in the schema ('organization identification string'), and schema description coverage is 100%. The description adds no extra meaning or format details beyond the schema, so the baseline of 3 applies.

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

Purpose3/5

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

The description 'Get/check organization.' identifies a verb and resource but is ambiguous: 'Get' and 'check' suggest different intents (retrieve vs. verify existence), and it does not clarify whether this targets a single organization versus a list. It distinguishes from sibling get_organizations only by singular form, which is implied but not explicit.

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?

No guidance is given on when to use this tool versus alternatives such as edubase_get_organizations or edubase_post_organization. There is no mention of context, prerequisites, or exclusions, leaving the agent to infer appropriate usage.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/EduBase/MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server