Skip to main content
Glama

create_user

Create a new user account in ServiceNow. Provide username, email, first name, and last name; optionally add job title and department.

Instructions

Create a new user account (requires WRITE_ENABLED=true)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_nameYesUnique username (login name)
emailYesEmail address
first_nameYesFirst name
last_nameYesLast name
titleNoJob title
departmentNoDepartment name or sys_id
Behavior4/5

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

Adds the configuration prerequisite (WRITE_ENABLED=true) beyond what annotations provide. Annotations indicate a write operation, but the description discloses the required setting, which is useful for the agent.

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?

Single, well-structured sentence that front-loads the purpose and includes a critical prerequisite. No unnecessary words.

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?

With 6 parameters and no output schema, the description lacks information about success/failure responses, validation rules, or additional behavioral details. Adequate but not comprehensive.

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?

All 6 parameters are fully described in the input schema (100% coverage). The description adds no extra parameter meaning; baseline score of 3 applies.

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?

Clearly states the tool creates a new user account. The verb 'create' and resource 'user account' are specific, and the purpose is unambiguous even among many sibling create tools.

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?

Mentions the requirement 'WRITE_ENABLED=true' but does not provide guidance on when to use this tool versus other create tools (e.g., create_group). No explicit alternatives or when-not scenarios.

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/tedorigawa001/ServiceNow-MCP'

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