EduBase MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

edubase_get_organization_competencies

Read-onlyIdempotent

Retrieve all competencies for a specified organization, provided the library and competencies features are enabled. Use this to access skill frameworks and competency data.

Instructions

List all competencies of an organization. Library and competencies must be enabled for the organization.

Input Schema

Name	Required	Description	Default
`organization`	Yes	organization identification string

Output Schema

Name	Required	Description	Default
`competencies`	Yes
`organization`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv2.0.9Oct 26, 2026

addedOutput schema / properties / competencies / items / properties / assignments / properties / jobs

Added value: +{
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}

changedOutput schema / properties / competencies / items / properties / assignments / required

Previous value: -[
-  "all",
-  "departments",
-  "members"
-]New value: +[
+  "all",
+  "departments",
+  "jobs",
+  "members"
+]

Changed19 schema fields changedv2.0.0Sep 15, 2026
- removedOutput schema / properties / competencies / items / properties / assigned / description
```
Removed value: -"number of visible members assigned to the competency"
```
- removedOutput schema / properties / competencies / items / properties / assignments / properties / all / description
```
Removed value: -"assigned to every member of the organization"
```
- removedOutput schema / properties / competencies / items / properties / assignments / properties / departments / description
```
Removed value: -"number of departments assigned to"
```
- removedOutput schema / properties / competencies / items / properties / assignments / properties / members / description
```
Removed value: -"number of members assigned to individually"
```
- removedOutput schema / properties / competencies / items / properties / competency / description
```
Removed value: -"competency identification string"
```
- removedOutput schema / properties / competencies / items / properties / description / description
```
Removed value: -"description of the competency (if set)"
```
- removedOutput schema / properties / competencies / items / properties / documents / description
```
Removed value: -"number of library documents attached"
```
- removedOutput schema / properties / competencies / items / properties / id / description
```
Removed value: -"external unique competency identifier (if set for the competency)"
```
- removedOutput schema / properties / competencies / items / properties / requirements / description
```
Removed value: -"number of requirements"
```
- removedOutput schema / properties / competencies / items / properties / status / description
```
Removed value: -"number of assigned members by their competency status"
```
- removedOutput schema / properties / competencies / items / properties / status / properties / completed / description
```
Removed value: -"completed"
```
- removedOutput schema / properties / competencies / items / properties / status / properties / due / description
```
Removed value: -"due soon"
```
- removedOutput schema / properties / competencies / items / properties / status / properties / expired / description
```
Removed value: -"expired"
```
- removedOutput schema / properties / competencies / items / properties / status / properties / outdated / description
```
Removed value: -"outdated"
```
- removedOutput schema / properties / competencies / items / properties / status / properties / overdue / description
```
Removed value: -"past the deadline"
```
- removedOutput schema / properties / competencies / items / properties / status / properties / progress / description
```
Removed value: -"in progress"
```
- removedOutput schema / properties / competencies / items / properties / status / properties / waiting / description
```
Removed value: -"waiting for completion"
```
- removedOutput schema / properties / competencies / items / properties / title / description
```
Removed value: -"title of the competency"
```
- removedOutput schema / properties / organization / description
```
Removed value: -"organization identification string"
```
Addedv1.2.17Sep 15, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive behavior, so the safety profile is covered. The description adds the feature-enablement prerequisite, which is genuine extra context, but says nothing about result size, ordering, or what happens with disabled features.

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?

Two short sentences: purpose first, precondition second. No filler, and the more actionable constraint is not buried.

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?

An output schema exists, so return values need not be described, and the enablement precondition is stated. For a single-parameter list tool this is close to sufficient, with only paging/volume behavior left implicit.

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?

Only one parameter with 100% schema description coverage, so the schema already explains 'organization identification string'. The description contributes no additional detail on identifier format or where to obtain it, so the baseline 3 applies.

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?

States a specific verb and resource: lists all competencies belonging to an organization. It is distinguishable from the nearby edubase_get_organization_competency_requirements by scope, though the description never names that sibling explicitly.

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?

Adds one real precondition – library and competencies must be enabled for the organization – which tells the agent the call will fail in an unconfigured org. Beyond that, there is no guidance on when to prefer this over related competency/requirement endpoints.

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

Deploy Server