EduBase MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

edubase_post_user

Create a new EduBase user account with username, name, email, and optional settings. Generates a random initial password when none is provided and returns account credentials.

Instructions

Create a new EduBase user account with a username, name, email address and optional details (group, language, timezone, custom fields, etc.). A random initial password is generated if none is given. Returns the user identification string, and the username and password for non-exam accounts.

Input Schema

TableJSON Schema

Name	Required	Description
`exam`	No	user is only allowed to login when accessing exams (default: false)
`color`	No	desired favorite color (default/branding/red/blue/yellow/green/purple/gray) (default: default)
`email`	Yes	valid email address
`group`	No	name of the user group
`phone`	No	valid phone number in format "+prefix number" without special characters
`custom`	No	custom field data, keyed by field name (sent as `custom_{field}`), only if the specified field is configured for the target EduBase instance
`gender`	No	gender ("male", "female", or "other")
`notify`	No	notify user via email (or SMS) (default: false)
`language`	No	desired account language (default: API application owner's language)
`password`	No	password (4-64 characters) (default: initial random password is automatically generated)
`template`	No	a template ID for the new account (default: none)
`timezone`	No	desired timezone (default: API application owner's timezone)
`username`	Yes	username (4-64 characters)
`birthdate`	No	date of birth
`full_name`	No	override automatic full name (1-255 characters)
`last_name`	Yes	last name (1-64 characters)
`first_name`	Yes	first name (1-64 characters)
`display_name`	No	override automatic display name (1-255 characters)
`must_change_password`	No	user is forced to change password on first login (default: false)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`user`	Yes
`password`	No
`username`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv2.0.0Sep 15, 2026
- removedOutput schema / properties / password / description
```
Removed value: -"password, only if exam=false"
```
- removedOutput schema / properties / user / description
```
Removed value: -"user identification string"
```
- removedOutput schema / properties / username / description
```
Removed value: -"username, only if exam=false"
```

Changed1 schema field changedv1.2.15Sep 2, 2026

addedInput schema / properties / custom

Added value: +{
+  "additionalProperties": {
+    "type": "string"
+  },
+  "description": "custom field data, keyed by field name (sent as `custom_{field}`), only if the specified field is configured for the target EduBase instance",
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}

Changed19 schema fields changedv1.1.2Mar 13, 2026

addedInput schema / $schema

Added value: +"http://json-schema.org/draft-07/schema#"

changedInput schema / properties / color / description

Previous value: -"desired favorite color (default/branding/red/blue/yellow/green/purple) (default: default)"New value: +"desired favorite color (default/branding/red/blue/yellow/green/purple/gray) (default: default)"

addedInput schema / properties / color / enum

Added value: +[
+  "default",
+  "branding",
+  "red",
+  "blue",
+  "yellow",
+  "green",
+  "purple",
+  "gray"
+]

addedInput schema / properties / display_name / maxLength
```
Added value: +255
```
addedInput schema / properties / display_name / minLength
```
Added value: +1
```
addedInput schema / properties / email / format
```
Added value: +"email"
```

addedInput schema / properties / email / pattern

Added value: +"^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"

addedInput schema / properties / first_name / maxLength
```
Added value: +64
```
addedInput schema / properties / first_name / minLength
```
Added value: +1
```
addedInput schema / properties / full_name / maxLength
```
Added value: +255
```
addedInput schema / properties / full_name / minLength
```
Added value: +1
```

addedInput schema / properties / gender / enum

Added value: +[
+  "male",
+  "female",
+  "other"
+]

addedInput schema / properties / last_name / maxLength
```
Added value: +64
```
addedInput schema / properties / last_name / minLength
```
Added value: +1
```
addedInput schema / properties / password / maxLength
```
Added value: +64
```
addedInput schema / properties / password / minLength
```
Added value: +4
```
addedInput schema / properties / username / maxLength
```
Added value: +64
```
addedInput schema / properties / username / minLength
```
Added value: +4
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "password": {
+      "description": "password, only if exam=false",
+      "type": "string"
+    },
+    "user": {
+      "description": "user identification string",
+      "type": "string"
+    },
+    "username": {
+      "description": "username, only if exam=false",
+      "type": "string"
+    }
+  },
+  "required": [
+    "user"
+  ],
+  "type": "object"
+}

First observedv1.0.22Feb 21, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations provide basic safety hints, and the description adds meaningful behavioral context: automatic random password generation when none is supplied, and the return semantics (user identification string plus username/password for non-exam accounts). This goes beyond what the annotations convey.

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 with no wasted words. The core purpose is front-loaded, and key behavioral notes are placed without obscuring the main function.

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 tool with 19 parameters, a nested object, and an output schema, the description provides a solid high-level summary and covers important return behavior. It does not detail every optional parameter, but the schema already handles that, so the description is complete enough for selecting and invoking the tool.

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 fully documents all parameters. The description enumerates a few optional field categories (group, language, timezone, custom fields) but does not add additional semantic detail beyond what the schema already provides.

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 opens with a specific verb ('Create') and resource ('EduBase user account'), and lists the key identifying fields. This clearly distinguishes it from sibling user tools like edubase_get_user, edubase_patch_user, and edubase_delete_user.

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?

The description implies the tool is for creating new accounts, which is distinct from update/delete/read siblings, but it does not explicitly state when to prefer this over alternatives or mention any exclusions or prerequisites. The usage context is clear enough from the verb, but no explicit guidance is provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server