Skip to main content
Glama
EduBase

EduBase MCP Server

Official
by EduBase
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

edubase_post_organization_members

Assign users to an organization, updating existing memberships and setting optional permissions or department.

Instructions

Assign user(s) to an organization. Updates memberships if already member of the 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
organizationYesorganization identification string
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. 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"
+}
  4. 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"
+]
  5. First observedv1.0.22

TDQS

B3.4/5.0
Behavior3/5

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

Beyond the annotations, the description adds a useful behavioral detail: if a user is already a member, the membership is updated instead of causing a duplicate or error. It does not mention return values, side effects, or required permissions, but the annotations already establish this is a mutating operation.

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 filler. The primary action is front-loaded, and the behavioral caveat about existing memberships is expressed in a single additional sentence.

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 complete parameter documentation and annotations covering mutability, the description is sufficient for an agent to invoke the tool correctly. The main gap is the lack of explicit differentiation from sibling tools and any mention of return behavior, but these are not critical for basic invocation.

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 input schema fully documents all seven parameters. The description does not add parameter-level guidance, which is acceptable but also not above the baseline for fully covered schemas.

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 and resource: 'Assign user(s) to an organization.' It also clarifies that existing memberships are updated rather than rejected. It does not explicitly name sibling alternatives, but the singular 'an organization' distinguishes it from tools like edubase_post_organizations_members and edubase_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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance about when to prefer this tool over closely related siblings such as edubase_post_organizations_members, edubase_post_user_organizations, or edubase_post_class_members. The description states what happens for existing members, but gives no invocation conditions, prerequisites, or exclusions.

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