Skip to main content
Glama
EduBase

EduBase MCP Server

Official
by EduBase
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

edubase_post_user_organizations

Assign a user to organizations, updating membership if already a member. Optionally set permissions, department, and notify user.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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_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.4/5.0
Behavior3/5

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

The description adds a key behavioral detail beyond annotations: 'Updates membership if already member of an organization,' which is not present in the annotation hints. However, it does not elaborate on side effects such as impact on competencies or permissions, and the openWorldHint suggests additional consequences are unstated. It provides some value but is not comprehensive.

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, direct sentences that front-load the primary action and then state the update behavior. There is zero fluff or redundant detail, making it highly efficient for an agent to parse.

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?

Despite having 7 parameters and no output schema, the description is extremely brief. It does not explain the operation's scope (e.g., multiple organizations via comma-separated list), the effect on existing permissions, or how it relates to sibling membership tools. The description leaves an agent without sufficient context to confidently invoke it correctly in a broader workflow.

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 all parameters are already well-documented with enums, defaults, and descriptions. The tool description itself adds no parameter-specific information. Per the rubric, with high coverage the baseline is 3, and the description does not go beyond that.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action: 'Assign user to organization(s)' with a specific verb and resource. It also clarifies behavior on existing membership, which distinguishes it from mere creation. The purpose is unambiguous and easy for an agent to grasp.

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 is given on when to use this tool versus the many similar sibling tools like edubase_post_organization_members or edubase_post_organizations_members. The description does not mention alternatives or conditions that would route an agent here over those tools, leaving selection to inference.

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