Skip to main content
Glama

create_user_with_certificate

Creates a pfSense local user and a CA-signed certificate, links them atomically, and rolls back the certificate if user creation fails.

Instructions

Create a pfSense user and a signed certificate, then link them atomically.

Generates a user certificate signed by the given CA, creates the local user with the certificate linked, and rolls back the certificate if user creation fails.

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>",
      "caref": "<caref>",
      "cert_descr": "<cert_descr>"
    },
    "name": "create_user_with_certificate"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesUsername (login name)
privNoList of privileges to assign to the user
carefYesReference ID of the Certificate Authority to sign the user cert
descrNoUser description / full name
keylenNoKey length in bits — 2048 or 4096 for RSA; 256 or 384 for ECDSA (default: 2048)
expiresNoAccount expiration date (MM/DD/YYYY format)
keytypeNoKey type — "RSA" or "ECDSA" (default: "RSA")RSA
disabledNoWhether the user account starts disabled (default: False)
lifetimeNoCertificate lifetime in days (default: 3650 = ~10 years)
passwordYesUser password
cert_descrYesDescriptive name for the generated certificate
digest_algNoDigest algorithm — sha256, sha384, sha512 (default: sha256)sha256
dn_commonnameNoCommon Name for the certificate (defaults to name if omitted)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: it discloses the rollback semantics, namely that the generated certificate is removed if user creation fails. It does not say what happens if a user with the same name already exists, or whether certificate creation failure leaves any partial state.

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 short sentences with the outcome front-loaded and the failure behavior immediately after. No filler, no restating of the tool name, and the atomicity claim is placed where an agent will see it first.

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

Completeness4/5

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

For a 13-parameter mutation tool, the description plus a full-coverage schema, annotations, and an output schema cover nearly everything needed to call it. The remaining gap is failure-mode detail on the user side (duplicate username, partial certificate state) for a tool whose selling point is atomicity.

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% across all 13 parameters, including key type, key length, lifetime, digest algorithm, and the CA reference, so the schema carries the full burden. The description adds no parameter-level meaning beyond restating that the certificate is signed by a given CA and linked to the user. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

The description states a specific compound verb and resource set: create a pfSense user AND a signed certificate, then link them. The composite scope implicitly distinguishes it from the bare create_user and create_certificate siblings, since neither of those alone produces both objects. It stops short of naming those siblings explicitly, so an agent must infer the boundary from the wording.

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?

Usage is only implied: the word 'atomically' and the rollback clause signal that this is the tool to pick when both a user and its certificate are wanted as a single unit. There is no explicit statement of when to prefer it over calling create_user and create_certificate separately, and no prerequisites (e.g. that the CA referenced by 'caref' must already exist) are called out.

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