Skip to main content
Glama

user_create

Create a new Operaton user account with profile details and password credentials; returns confirmation on success.

Instructions

Create a new Operaton user account with profile (id, firstName, lastName, email) and credentials (password). Returns confirmation on success.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "user_create"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.3.0
    • addedInput schema / additionalProperties
      Added value: +{}
  2. First observedv1.1.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden. Beyond 'Returns confirmation on success' it says nothing about permission requirements, uniqueness constraints on id, password policy, or what happens if the user already exists — all material for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact sentences, front-loaded with the action and the payload, with no filler. Slightly dense packing of five field names into one clause, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a create mutation with no annotations, no output schema, and an empty input schema, the description covers the essentials of what is created. It falls short on error behavior, permissions, and field constraints, which an agent would need before invoking it confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema is an empty object, so the description is the only source naming the expected fields (id, firstName, lastName, email, password). That adds real value, but it gives no format, required/optional, or constraint detail for any of them.

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?

States a specific verb and resource ('Create a new Operaton user account') and enumerates what the account carries (profile fields plus password). It is clearly distinguishable from siblings like user_updateProfile or user_delete, though it never names those alternatives explicitly.

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 on when to use this versus user_updateProfile or user_getProfile, and no prerequisites such as required admin permissions or whether the account is created active/locked. The creation intent is implied by the verb but no conditions or exclusions are given.

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