Skip to main content
Glama

edubase_post_user_organizations

Assign a user to one or more organizations, updating existing membership when needed. Optionally set job role, department, permissions, restrictions, and send notifications.

Instructions

Assign user to organization(s). Updates membership if already member of an organization.

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>",
      "organizations": "<organizations>"
    },
    "name": "edubase_post_user_organizations"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobNooptional name of job role (or its external identifier if no job role has this name), empty string removes the job role, the job role is kept when not specified or unknown in an organization, the competency assignments of the members with another job role are updated, the competencies they only had through their previous job role are lost
userYesuser identification string
notifyNonotify user (default: false)
departmentNooptional name of department (or its external identifier if no department has this name), the competency assignments of the members moved to another department are updated, the competencies they only had through their previous department are lost
organizationsYescomma-separated list of organization identification strings
permission_customNocustomize the permission levels of the members inside the department (only used together with department, the permission_ fields not specified default to the ones of the department), members with custom permission levels keep them when the permission levels of the department are changed, set to false to make the members follow the permission levels of the department again, when not specified, custom permission levels are kept for the members staying in the same department and removed when moved to another department
permission_contentNooptional permission level to contents in organization (none / view / report / control / modify / grant / admin) (default: none)
permission_membersNooptional permission level to members in organization (none / department / organization) (default: none)
restriction_libraryNorestrict the members from managing the library of the organization (documents, versions and types), even with a sufficient permission level (only available if the library is enabled in the organization, ignored otherwise), left unchanged when not specified (default for new members: false)
permission_organizationNooptional permission level to organization (member / teacher / reporter / supervisor / admin) (default: member)
restriction_competenciesNorestrict the members from managing the competencies of the organization and its members (competencies, requirements, assignments, completions, expiry dates and attachments), even with a sufficient permission level (only available if the library is enabled in the organization, ignored otherwise), left unchanged when not specified (default for new members: false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.0.9
    • addedInput schema / properties / job
      Added value: +{
      +  "description": "optional name of job role (or its external identifier if no job role has this name), empty string removes the job role, the job role is kept when not specified or unknown in an organization, the competency assignments of the members with another job role are updated, the competencies they only had through their previous job role are lost",
      +  "type": "string"
      +}
    • addedInput schema / properties / permission_custom
      Added value: +{
      +  "description": "customize the permission levels of the members inside the department (only used together with department, the permission_ fields not specified default to the ones of the department), members with custom permission levels keep them when the permission levels of the department are changed, set to false to make the members follow the permission levels of the department again, when not specified, custom permission levels are kept for the members staying in the same department and removed when moved to another department",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / restriction_competencies
      Added value: +{
      +  "description": "restrict the members from managing the competencies of the organization and its members (competencies, requirements, assignments, completions, expiry dates and attachments), even with a sufficient permission level (only available if the library is enabled in the organization, ignored otherwise), left unchanged when not specified (default for new members: false)",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / restriction_library
      Added value: +{
      +  "description": "restrict the members from managing the library of the organization (documents, versions and types), even with a sufficient permission level (only available if the library is enabled in the organization, ignored otherwise), left unchanged when not specified (default for new members: false)",
      +  "type": "boolean"
      +}
  2. Changed1 schema field changedv1.2.17
    • changedInput schema / properties / department / description
      Previous value: -"optional name of department, the competency assignments of the members moved to another department are updated, the competencies they only had through their previous department are lost"New value: +"optional name of department (or its external identifier if no department has this name), the competency assignments of the members moved to another department are updated, the competencies they only had through their previous department are lost"
  3. Changed1 schema field changedv1.2.16
    • changedInput schema / properties / department / description
      Previous value: -"optional name of department"New value: +"optional name of department, the competency assignments of the members moved to another department are updated, the competencies they only had through their previous department are lost"
  4. Addedv1.2.9
  5. Removedv1.2.8
  6. Changed3 schema fields changedv1.1.2
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / properties / permission_content / enum
      Added value: +[
      +  "none",
      +  "view",
      +  "report",
      +  "control",
      +  "modify",
      +  "grant",
      +  "admin"
      +]
    • addedInput schema / properties / permission_organization / enum
      Added value: +[
      +  "member",
      +  "teacher",
      +  "reporter",
      +  "supervisor",
      +  "admin"
      +]
  7. First observedv1.0.22

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true, so the safety profile is carried structurally. The description adds the genuinely useful fact that this is an upsert rather than a pure create. However it omits the consequential behaviors the schema hints at — competency loss on job-role change, permission resets on department moves, and the notify side effect — which materially shape how an agent should call this.

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, front-loaded with the action and followed by the conditional-update clause; no waste or filler. It is efficient, though for an 11-parameter mutation tool the terseness borders on under-specification.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a high-complexity mutation tool with 11 parameters that can change permissions, strip competencies, and optionally notify users, and the description covers none of that. Annotations flag the operation as non-destructive, but the description does not warn about the cascading membership side effects an agent should understand before calling it.

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% and every one of the 11 parameters (job, department, permission_*, restriction_*, notify) is documented in detail in the schema itself. The description adds nothing about parameters, so the baseline 3 is the correct ceiling here.

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 ("Assign user to organization(s)") and adds the upsert nuance ("Updates membership if already member"). That is enough to separate it from edubase_delete_user_organizations and edubase_get_user_organizations, but it does not explicitly distinguish it from the closely named bulk sibling edubase_post_organizations_members.

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?

The description implies its usage by naming the action, but gives no explicit when-to-use, prerequisites, or alternative routing. With sibling tools like edubase_delete_user_organizations, edubase_post_user_classes and edubase_post_organizations_members available, an agent gets no help choosing between them.

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