Skip to main content
Glama

edubase_post_user

Create a new EduBase user account with username, first/last name, and email, plus optional attributes such as password, group, or exam access.

Instructions

Create new EduBase user account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
usernameYesusername (4-64 characters)
passwordNopassword (4-64 characters) (default: initial random password is automatically generated)
first_nameYesfirst name (1-64 characters)
last_nameYeslast name (1-64 characters)
full_nameNooverride automatic full name (1-255 characters)
display_nameNooverride automatic display name (1-255 characters)
emailYesvalid email address
phoneNovalid phone number in format "+prefix number" without special characters
genderNogender ("male", "female", or "other")
birthdateNodate of birth
examNouser is only allowed to login when accessing exams (default: false)
groupNoname of the user group
templateNoa template ID for the new account (default: none)
languageNodesired account language (default: API application owner's language)
timezoneNodesired timezone (default: API application owner's timezone)
colorNodesired favorite color (default/branding/red/blue/yellow/green/purple/gray) (default: default)
must_change_passwordNouser is forced to change password on first login (default: false)
notifyNonotify user via email (or SMS) (default: false)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
userYesuser identification string
usernameNousername, only if exam=false
passwordNopassword, only if exam=false
Behavior2/5

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

The description does not disclose behavioral details beyond what annotations indicate (e.g., no warning about non-idempotency, no mention of return value or side effects). Annotations show readOnlyHint=false and idempotentHint=false, but the description adds no context.

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 a single, concise sentence that is front-loaded with the core purpose, with no unnecessary words.

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?

Given the high parameter count (18) and presence of an output schema, the description is too minimal. It does not explain the return value, success/failure behavior, or important details like automatic password generation, which are partially covered in param descriptions but not in the tool description.

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 description does not need to add param info. It adds no extra meaning beyond the schema, meeting the baseline.

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 verb 'Create' and resource 'new EduBase user account', which is specific and distinguishes this tool from siblings (e.g., edubase_delete_user, edubase_patch_user).

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 guidelines provided about when to use this tool versus alternatives like edubase_patch_user or edubase_delete_user, nor any prerequisites or conditions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/EduBase/MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server