Skip to main content
Glama

create_user

Creates a new local pfSense user account with password, privileges, certificates, expiration, and optional SSH keys or disabled status.

Instructions

Create a new pfSense local user

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": {
      "name": "<name>",
      "password": "<password>"
    },
    "name": "create_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
uidNoExplicit unix UID to assign — use when pfSense nextuid counter is stale/colliding
certNoList of certificate refids to associate with the user
nameYesUsername (login name)
privNoList of privileges to assign (e.g., ["page-all", "user-shell-access"])
descrNoUser description / full name
expiresNoAccount expiration date (MM/DD/YYYY format)
disabledNoWhether the user account starts disabled
ipsecpskNoIPsec Pre-Shared Key for this user
passwordYesUser password
authorizedkeysNoSSH authorized public keys (base64 encoded)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations declare readOnlyHint=false and destructiveHint=false, so the description should add context such as whether the user lands in the local auth store, whether it fails on duplicate names, or what permissions are required. Instead it restates the title-level action only; the presence of the 'cert' parameter also raises a question the description never resolves about overlap with create_user_with_certificate.

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?

A single front-loaded sentence with no padding. It is efficient, though the brevity borders on under-specification rather than crispness.

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?

For a ten-parameter mutation tool with an output schema, the description covers only the bare action. It omits how this relates to create_user_with_certificate and create_freeradius_user, says nothing about password constraints, whether the account is immediately usable, or required privileges — all of which an agent needs to select correctly.

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 all ten parameters including 'uid', 'priv', and 'expires' are documented in the schema itself; that establishes the baseline of 3. The description adds no parameter meaning, so it neither compensates nor detracts.

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 pfSense local user'), and the word 'local' signals the local user database as opposed to sibling RADIUS tools like create_freeradius_user. It does not distinguish itself from create_user_with_certificate, which is a genuine ambiguity given this tool also accepts a 'cert' parameter.

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 explicit when-to-use guidance, no prerequisites, and no alternatives named. The agent must infer from the word 'local' that this is not the RADIUS variant, and has no help deciding between this and create_user_with_certificate.

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