Skip to main content
Glama
EduBase

EduBase MCP Server

Official
by EduBase
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

edubase_post_organizations_members

Assign users to organizations, updating memberships when users are already members. Configure permission levels, department, and notification settings in a single API call.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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
organizationsYescomma-separated list of organization identification strings
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)
permission_organizationNooptional permission level to organization (member / teacher / reporter / supervisor / admin) (default: member)

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
  2. 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"
  3. Addedv1.2.9
  4. Removedv1.2.8
  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

B3.3/5.0
Behavior3/5

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

The description discloses the upsert behavior ('Updates memberships if already member'), which is valuable and goes beyond the annotations that only indicate a write operation. However, it does not mention side effects like permission changes, notification behavior, or department-related competency updates that are hinted by parameters.

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 concise sentences, front-loaded with the primary action and a key behavioral note. No redundant information.

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?

For a tool with 7 parameters, 3 enums, and no output schema, the description is minimal. It covers the core action but omits guidance on optional parameters, side effects, or which sibling tool to choose, leaving the agent to rely heavily on the schema.

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 coverage is 100%, so each parameter already has a description. The tool description does not add additional semantic meaning beyond the schema, but it does reinforce the concept of updating memberships, which is marginally helpful.

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 uses a specific verb ('Assign') and resource ('user(s) to organization(s)'), and clarifies the upsert behavior. It is clear but does not explicitly differentiate from similar siblings like edubase_post_organization_members or edubase_post_user_organizations, leaving some ambiguity.

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?

No guidance on when to use this tool over alternatives. It does not mention exclusions, prerequisites, or compare with sibling tools that handle similar assignments.

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