Skip to main content
Glama

edubase_post_organization_members

Assign users to an organization or update existing memberships. Set job roles, departments, and permission levels for members.

Instructions

Assign user(s) to an organization. Updates memberships if already member of the 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": {
      "organization": "<organization>",
      "users": "<users>"
    },
    "name": "edubase_post_organization_members"
  }
}

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, an unknown job role is an error, the competency assignments of the members with another job role are updated, the competencies they only had through their previous job role are lost
usersYescomma-separated list of user identification strings
notifyNonotify users (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, should not be used together with the permission_ fields, unless permission_custom is set
organizationYesorganization identification string
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. Changed5 schema fields changedv2.0.9
    • changedInput schema / properties / department / description
      Previous 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"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, should not be used together with the permission_ fields, unless permission_custom is set"
    • 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, an unknown job role is an error, 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. Changed1 schema field changedv1.2.9
    • addedInput schema / properties / permission_members
      Added value: +{
      +  "description": "optional permission level to members in organization (none / department / organization) (default: none)",
      +  "enum": [
      +    "none",
      +    "department",
      +    "organization"
      +  ],
      +  "type": "string"
      +}
  5. 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"
      +]
  6. 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 disclose that this is a non-read-only, open-world mutation. The description adds useful upsert context for existing members. However, it does not mention permission requirements, notification behavior, or the competency-loss side effects described in the schema.

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?

The description is two short sentences with no waste. The primary action is front-loaded, followed by the important membership-update detail.

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

Completeness3/5

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

The description covers the core operation and upsert behavior, but it is thin for an 11-parameter mutation tool. It does not summarize the major optional capabilities around jobs, departments, permissions, and restrictions, nor does it describe response 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?

Schema description coverage is 100%, so the schema already explains all 11 parameters in detail. The description does not add parameter-level meaning beyond that. Baseline 3 is appropriate when the schema carries the parameter semantics.

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?

The description gives a clear verb and resource: assign users to an organization. It also clarifies the upsert behavior when the user is already a member. It does not explicitly distinguish itself from related siblings such as get/delete members or post_user_organizations.

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 purpose: use this to assign users to an organization. The note about updating existing memberships helps clarify behavior, but there is no explicit when-to-use guidance, exclusions, or named alternatives.

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