Skip to main content
Glama
EduBase

EduBase MCP Server

Official
by EduBase
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

edubase_get_integrations

Read-onlyIdempotent

List integrations owned by the EduBase account, returning IDs, external identifiers, and titles to identify connected systems.

Instructions

List owned and managed integrations. Returns integration 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
integrationsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.0.0
    • removedOutput schema / properties / integrations / items / properties / id / description
      Removed value: -"external unique integration identifier (if set for the integration)"
    • removedOutput schema / properties / integrations / items / properties / integration / description
      Removed value: -"integration identification string"
    • removedOutput schema / properties / integrations / items / properties / title / description
      Removed value: -"title of the integration"
  2. Changed3 schema fields changedv1.2.15
    • removedOutput schema / properties / integrations / items / properties / name
      Removed value: -{
-  "description": "title of the integration",
-  "type": "string"
-}
    • addedOutput schema / properties / integrations / items / properties / title
      Added value: +{
+  "description": "title of the integration",
+  "type": "string"
+}
    • changedOutput schema / properties / integrations / items / required
      Previous value: -[
-  "integration",
-  "name"
-]New value: +[
+  "integration",
+  "title"
+]
  3. 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": {
+    "integrations": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "id": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "external unique integration identifier (if set for the integration)"
+          },
+          "integration": {
+            "description": "integration identification string",
+            "type": "string"
+          },
+          "name": {
+            "description": "title of the integration",
+            "type": "string"
+          }
+        },
+        "required": [
+          "integration",
+          "name"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "integrations"
+  ],
+  "type": "object"
+}
  4. First observedv1.0.22

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds the return-field summary and the owned/managed scope, but it does not disclose pagination behavior, search-mode semantics, or any caveats about what 'owned and managed' means.

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 sentences: the first names the operation and scope, the second summarizes the return payload. There is no filler, repetition beyond the title, or unnecessary detail, and the core action is front-loaded.

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?

The input schema fully documents all three optional parameters, the output schema exists, and annotations provide the safety profile. The description adds enough scope and return context for a simple list operation, so nothing essential is missing for an agent to 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?

Schema description coverage is 100%, so page, limit, and search are already fully documented with types, defaults, and the search-mode caveat. The description does not add parameter-level meaning, which is acceptable given the schema's completeness.

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 states a specific verb and resource: 'List owned and managed integrations'. It also summarizes the returned data (identification strings, external identifiers, titles), which clearly distinguishes this plural-list operation from the singular edubase_get_integration and other integration-related tools.

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 intended use is implied by the verb 'List' and the resource scope 'owned and managed integrations', but there is no explicit statement about when to choose this over edubase_get_integration or get_integration_keys. 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

Other Tools