Skip to main content
Glama
EduBase

EduBase MCP Server

Official
by EduBase
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

edubase_post_user_group

Move a user to a different user group by group code and confirm whether the group was changed.

Instructions

Move a user to another user group, identified by its code. Returns whether the group was changed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
userYesuser identification string
groupYesuser group code

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
userYes
changedYes
successYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.0.0
    • removedOutput schema / properties / changed / description
      Removed value: -"group has been changed"
    • removedOutput schema / properties / success / description
      Removed value: -"operation is successful"
    • removedOutput schema / properties / user / description
      Removed value: -"the user identification string"
  2. Changed2 schema fields changedv1.1.2
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "changed": {
+      "description": "group has been changed",
+      "type": "boolean"
+    },
+    "success": {
+      "description": "operation is successful",
+      "type": "boolean"
+    },
+    "user": {
+      "description": "the user identification string",
+      "type": "string"
+    }
+  },
+  "required": [
+    "user",
+    "success",
+    "changed"
+  ],
+  "type": "object"
+}
  3. First observedv1.0.22

TDQS

A4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=false and destructiveHint=false, covering the mutation and safety profile. The description adds useful context by specifying that the group is identified by a code and that the tool returns whether the group was changed. However, it does not disclose edge-case behavior, such as what happens if the user or group does not exist, or whether membership in the previous group is removed.

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 short, focused sentences with no filler. The core action is front-loaded, and every clause adds information: the operation, the identification scheme, and the return value.

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?

For a two-parameter operation with a provided output schema, the description is sufficiently complete: it states the action, identifies how the group is selected, and mentions the return value. It omits error-handling details, but those are not critical for such a straightforward move operation.

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?

Both parameters have complete schema descriptions ('user identification string' and 'user group code'), so the baseline of 3 applies. The tool description only reinforces that the group is referenced by its code, which is already in the schema, and adds no additional format, example, or relationship detail.

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 states a specific verb ('Move') and target resource ('user to another user group'), and adds the identifying scheme ('by its code') and the return value. This clearly distinguishes it from sibling GET tools like edubase_get_user_group and association tools like edubase_post_user_classes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

The description gives clear context for when to use the tool: to relocate a user to a different group. It doesn't mention alternatives or exclusions, but the use of 'Move' rather than 'Add' or 'Get' implicitly separates it from related actions, and no other sibling tool appears to handle this exact operation.

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