mcp-freeipa

add_user

Create a new FreeIPA user account with required login UID, first name, and surname. Optionally set email, title, department, and initial password.

Instructions

Create a new FreeIPA user account.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "uid": "<uid>",
      "givenname": "<givenname>",
      "sn": "<sn>"
    },
    "name": "add_user"
  }
}

Input Schema

Name	Required	Description
`cn`	No	Full display name — defaults to 'givenname sn' if not provided
`sn`	Yes	Last name (surname) of the user
`uid`	Yes	Login name (UID) for the new user
`mail`	No	Email address
`title`	No	Job title
`givenname`	Yes	First name of the user
`department`	No	Department or organisational unit
`userpassword`	No	Initial password for the user

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 6, 2026

TDQS

B3.4/5.0

Behavior2/5

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

With no annotations, the description must carry behavioral disclosure, but it only restates the core action. It does not mention side effects, administrative privileges, duplicate UID behavior, password policy requirements, or what happens after creation. 'Create' signals a mutation, but no meaningful behavioral context beyond that is disclosed.

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, front-loaded sentence with no wasted words. It communicates the essential action immediately and does not include redundant information.

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?

Despite full schema coverage, the description omits important operational context for a write operation: required privileges, uniqueness constraints, password handling, and what the tool returns or does after creation. There is no output schema and no annotations to fill these gaps, so the description is not sufficiently complete for a provisioning 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?

The input schema covers 100% of parameters with descriptions, so the baseline is 3. The description adds no parameter-level meaning 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 uses a specific verb ('Create') and resource ('FreeIPA user account'), clearly identifying the operation. It is unambiguous and distinguishable from the sibling tools, which cover retrieval, listing, deletion, and state changes.

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 usage for provisioning a new user, but it does not explicitly state when to choose this tool over related operations such as reset_password, enable_user, or add_user_to_group. No exclusions or alternative routing are provided, so the usage context is only implicit.

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