EduBase MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

edubase_get_organization_competency_requirements

Read-onlyIdempotent

Retrieve competency requirements in priority order for an organization, revealing which skills are most critical to address.

Instructions

List the requirements of a competency, ordered by their priority. Library and competencies must be enabled for the organization of the competency.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`competency`	Yes	competency identification string (or its external identifier when organization is specified)
`organization`	No	optional organization identification string

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	No
`title`	Yes
`competency`	Yes
`organization`	Yes
`requirements`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed28 schema fields changedv2.0.0Sep 15, 2026

removedOutput schema / properties / competency / description
```
Removed value: -"competency identification string"
```

removedOutput schema / properties / id / description

Removed value: -"external unique competency identifier (if set for the competency)"

removedOutput schema / properties / organization / description
```
Removed value: -"organization identification string"
```
removedOutput schema / properties / requirements / description
```
Removed value: -"requirements ordered by their priority"
```

changedOutput schema / properties / requirements / items / properties / class / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "class": {
-        "description": "class identification string",
-        "type": "string"
-      },
-      "id": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "description": "external unique class identifier (if set for the class)"
-      },
-      "title": {
-        "description": "title of the class",
-        "type": "string"
-      }
-    },
-    "required": [
-      "class",
-      "title"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "class": {
+        "type": "string"
+      },
+      "id": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "title": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "class",
+      "title"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / requirements / items / properties / class / description

Removed value: -"the required class (only present if type is class, null if the class is not available)"

removedOutput schema / properties / requirements / items / properties / deadline / description
```
Removed value: -"deadline of the requirement (only present if a deadline is configured)"
```
removedOutput schema / properties / requirements / items / properties / deadline / properties / date / description
```
Removed value: -"fixed deadline (only if type is date)"
```
removedOutput schema / properties / requirements / items / properties / deadline / properties / days / description
```
Removed value: -"number of days available to complete the requirement (only if type is days)"
```
removedOutput schema / properties / requirements / items / properties / deadline / properties / type / description
```
Removed value: -"type of the deadline"
```
removedOutput schema / properties / requirements / items / properties / description / description
```
Removed value: -"description of the requirement (only present if set for the requirement)"
```

changedOutput schema / properties / requirements / items / properties / document / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "archived": {
-        "description": "document is archived",
-        "type": "boolean"
-      },
-      "document": {
-        "description": "document identification string",
-        "type": "string"
-      },
-      "prefix": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "description": "prefix of the document"
-      },
-      "title": {
-        "description": "title of the document",
-        "type": "string"
-      }
-    },
-    "required": [
-      "document",
-      "title",
-      "archived"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "archived": {
+        "type": "boolean"
+      },
+      "document": {
+        "type": "string"
+      },
+      "prefix": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "title": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "document",
+      "title",
+      "archived"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / requirements / items / properties / document / description

Removed value: -"the required library document (only present if type is document, null if the document is not available)"

removedOutput schema / properties / requirements / items / properties / documents / description

Removed value: -"identification strings of the library documents attached to the requirement (only present if there are any)"

changedOutput schema / properties / requirements / items / properties / exam / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "exam": {
-        "description": "exam identification string",
-        "type": "string"
-      },
-      "id": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "description": "external unique exam identifier (if set for the exam)"
-      },
-      "title": {
-        "description": "title of the exam",
-        "type": "string"
-      }
-    },
-    "required": [
-      "exam",
-      "title"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "exam": {
+        "type": "string"
+      },
+      "id": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "title": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "exam",
+      "title"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / requirements / items / properties / exam / description

Removed value: -"the required exam (only present if type is exam, null if the exam is not available)"

removedOutput schema / properties / requirements / items / properties / optional / description
```
Removed value: -"requirement is optional"
```
removedOutput schema / properties / requirements / items / properties / requirement / description
```
Removed value: -"requirement identification string"
```
removedOutput schema / properties / requirements / items / properties / title / description
```
Removed value: -"title of the requirement"
```
removedOutput schema / properties / requirements / items / properties / todo / description
```
Removed value: -"the required task (only present if type is todo)"
```
removedOutput schema / properties / requirements / items / properties / todo / properties / attachments / description
```
Removed value: -"attachments can be uploaded"
```
removedOutput schema / properties / requirements / items / properties / todo / properties / educators / description
```
Removed value: -"educators of the training (only present if type is training, visible users only)"
```
removedOutput schema / properties / requirements / items / properties / todo / properties / educators / items / properties / name / description
```
Removed value: -"name of the educator"
```
removedOutput schema / properties / requirements / items / properties / todo / properties / educators / items / properties / user / description
```
Removed value: -"user identification string"
```
removedOutput schema / properties / requirements / items / properties / todo / properties / fields / description
```
Removed value: -"labels of the fields to fill (only present if type is default)"
```
removedOutput schema / properties / requirements / items / properties / todo / properties / type / description
```
Removed value: -"type of the task"
```
removedOutput schema / properties / requirements / items / properties / type / description
```
Removed value: -"type of the requirement"
```
removedOutput schema / properties / title / description
```
Removed value: -"title of the competency"
```

Addedv1.2.17Sep 15, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover read-only, non-destructive, and idempotent behavior. The description adds the ordering guarantee and the prerequisite about library/competency enablement, which are useful behavioral details beyond the structured annotations. No contradiction.

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 sentences with no filler. The primary action is front-loaded, and the prerequisite is stated in a single follow-up clause. Every word contributes.

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?

With an output schema present, return format doesn't need description. The description covers purpose and prerequisites. It could mention error behavior when prerequisites are unmet, but that's a minor omission for a read-only list operation.

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% – both 'competency' and 'organization' have explicit descriptions in the schema. The description adds minimal additional parameter meaning, only hinting that organization is relevant to the competency's context. Baseline 3 is appropriate.

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 ('List'), a precise resource ('requirements of a competency'), and a clear ordering ('by their priority'). It distinguishes itself from the sibling tool edubase_get_organization_competencies, which lists competencies themselves, not their requirements.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

The description provides a clear precondition: 'Library and competencies must be enabled for the organization of the competency.' This tells the agent when the tool is applicable. It doesn't explicitly mention alternatives, but the distinct resource (requirements vs. competencies) makes the use case unambiguous.

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

Deploy Server