Skip to main content
Glama
moneyforward-i

Admina MCP Server

create_identity

Create a new employee identity in the organization with required status, type, and name fields. Optionally add email, department, manager, and custom details.

Instructions

Create a new identity in the organization. Requires employeeStatus, employeeType, firstName, and lastName. Optional: displayName, primaryEmail, department, jobTitle, employeeId, lifecycle, customFields, manager, etc.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
employeeStatusYesExtended status of the employee
employeeTypeYesType of the employee
firstNameYesFirst name of the employee
lastNameYesLast name of the employee
managementTypeNoManagement type of the employee
displayNameNoDisplay name of the employee
primaryEmailNoPrimary email of the employee
secondaryEmailsNoSecondary emails of the employee
companyNameNoCompany name of the employee
workLocationNoWork location of the employee
departmentNoDepartment of the employee
jobTitleNoJob title of the employee
employeeIdNoEmployee ID of the employee
lifecycleNoLifecycle of the employee
noteNoNotes of the employee
customFieldsNoCustom fields of the employee
managerNoManager of the employee
Behavior2/5

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

The description does not disclose behavioral traits such as idempotency, permissions required, error handling, or return value. For a creation tool with no annotations, this leaves the agent uncertain about side effects.

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 efficient sentences: first provides purpose, second lists requirements. No redundant words, and the critical information is front-loaded.

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 17 parameters and no output schema, the description should explain return value, constraints, and usage nuances. It only lists fields, leaving the agent uninformed about the outcome or process.

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 coverage is 100%, so the baseline is 3. The description reiterates required/optional status from the schema but adds no new semantic meaning beyond listing fields.

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 'Create a new identity in the organization' and lists required and optional fields, making the tool's purpose unambiguous and distinct from siblings like update or delete.

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?

While the description specifies required vs. optional fields, it lacks guidance on when to use this tool over alternatives (e.g., bulk_create or merge) and provides no context on prerequisites or when not to use it.

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/moneyforward-i/admina-mcp-server'

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