Skip to main content
Glama

edubase_get_user_organizations

Read-onlyIdempotent

Retrieve the organizations a user belongs to, including titles, links, department, permission levels, and management restrictions.

Instructions

List the organizations a user is member of, with their titles, links, the department of the user, the permission levels and the management restrictions.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "user": "<user>"
    },
    "name": "edubase_get_user_organizations"
  }
}

Input Schema

NameRequiredDescriptionDefault
userYesuser identification string

Output Schema

NameRequiredDescriptionDefault
organizationsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.0.9
    • addedOutput schema / properties / organizations / items / properties / job
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • addedOutput schema / properties / organizations / items / properties / permission / properties / custom
      Added value: +{
      +  "type": "boolean"
      +}
    • changedOutput schema / properties / organizations / items / properties / permission / required
      Previous value: -[
      -  "organization",
      -  "content",
      -  "members"
      -]New value: +[
      +  "organization",
      +  "content",
      +  "members",
      +  "custom"
      +]
    • addedOutput schema / properties / organizations / items / properties / restriction
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "competencies": {
      +      "type": "boolean"
      +    },
      +    "library": {
      +      "type": "boolean"
      +    }
      +  },
      +  "type": "object"
      +}
  2. Changed9 schema fields changedv2.0.0
    • removedOutput schema / properties / organizations / items / properties / department / description
      Removed value: -"name of the department (if member)"
    • removedOutput schema / properties / organizations / items / properties / id / description
      Removed value: -"external unique organization identifier (if set for the organization)"
    • removedOutput schema / properties / organizations / items / properties / link / description
      Removed value: -"link to the organization manager page"
    • removedOutput schema / properties / organizations / items / properties / organization / description
      Removed value: -"organization identification string"
    • removedOutput schema / properties / organizations / items / properties / permission / description
      Removed value: -"permissions"
    • removedOutput schema / properties / organizations / items / properties / permission / properties / content / description
      Removed value: -"permission level to contents in organization"
    • removedOutput schema / properties / organizations / items / properties / permission / properties / members / description
      Removed value: -"permission level to members in organization"
    • removedOutput schema / properties / organizations / items / properties / permission / properties / organization / description
      Removed value: -"permission level to organization"
    • removedOutput schema / properties / organizations / items / properties / title / description
      Removed value: -"title of the organization"
  3. Changed3 schema fields changedv1.2.15
    • removedOutput schema / properties / organizations / items / properties / name
      Removed value: -{
      -  "description": "title of the organization",
      -  "type": "string"
      -}
    • addedOutput schema / properties / organizations / items / properties / title
      Added value: +{
      +  "description": "title of the organization",
      +  "type": "string"
      +}
    • changedOutput schema / properties / organizations / items / required
      Previous value: -[
      -  "organization",
      -  "name",
      -  "link",
      -  "permission"
      -]New value: +[
      +  "organization",
      +  "title",
      +  "link",
      +  "permission"
      +]
  4. Addedv1.2.9
  5. Removedv1.2.8
  6. 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": {
      +    "organizations": {
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "department": {
      +            "anyOf": [
      +              {
      +                "type": "string"
      +              },
      +              {
      +                "type": "null"
      +              }
      +            ],
      +            "description": "name of the department (if member)"
      +          },
      +          "id": {
      +            "anyOf": [
      +              {
      +                "type": "string"
      +              },
      +              {
      +                "type": "null"
      +              }
      +            ],
      +            "description": "external unique organization identifier (if set for the organization)"
      +          },
      +          "link": {
      +            "description": "link to the organization manager page",
      +            "type": "string"
      +          },
      +          "name": {
      +            "description": "title of the organization",
      +            "type": "string"
      +          },
      +          "organization": {
      +            "description": "organization identification string",
      +            "type": "string"
      +          },
      +          "permission": {
      +            "additionalProperties": false,
      +            "description": "permissions",
      +            "properties": {
      +              "content": {
      +                "description": "permission level to contents in organization",
      +                "type": "string"
      +              },
      +              "organization": {
      +                "description": "permission level to organization",
      +                "type": "string"
      +              }
      +            },
      +            "required": [
      +              "organization",
      +              "content"
      +            ],
      +            "type": "object"
      +          }
      +        },
      +        "required": [
      +          "organization",
      +          "name",
      +          "link",
      +          "permission"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "organizations"
      +  ],
      +  "type": "object"
      +}
  7. First observedv1.0.22

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the safety profile is covered. The description adds what the payload contains (titles, links, department, permission levels, management restrictions), but nothing about pagination, empty results, or error behavior.

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?

A single front-loaded sentence with no preamble or filler. The trailing enumeration of return fields is somewhat redundant with the output schema but is compact and readable.

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 rich annotations, one required parameter and an output schema, the definition covers what an agent needs to select and call the tool. Minor gaps remain around identifier format and result-size behavior.

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 and the schema documents it fully at 100% coverage, so the baseline is 3. The description says nothing extra about the 'user' identifier format (ID vs email vs username), leaving the agent dependent on the schema's terse 'user identification string'.

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 (List) and a precisely scoped resource (organizations a user is member of), which separates it from edubase_get_organizations. It does not explicitly name that sibling, so differentiation is inferred rather than stated.

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?

Usage is implied by the per-user scope, but there is no explicit when-to-use guidance and no mention of the write/delete siblings (edubase_post_user_organizations, edubase_delete_user_organizations) or of alternative listing tools.

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