Skip to main content
Glama
RadiusStack MCP Server

RadiusStack MCP Server

by deangoldhill

Create RadiusStack user

radiusstack_create_user

Create a RADIUS user in RadiusStack with username, password, and optional profile, plan, static IP, TOTP, or disabled status; confirm settings before calling.

Instructions

Create a RADIUS user. This changes RadiusStack. Confirm the requested username and settings before calling.

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

Input Schema

NameRequiredDescriptionDefault
planIdNoOptional RadiusStack plan ID.
profileNoOptional RadiusStack profile name.
disabledNoWhether RadiusStack should reject authentication for this user.
passwordYes
staticIpNoOptional static IPv4 address.
usernameYesRadiusStack username
totpEnabledNoWhether to enable RadiusStack TOTP for this user.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so 'This changes RadiusStack' is largely a restatement. The confirmation instruction is a genuinely useful safety cue beyond the annotations, but the description is silent on the important create-specific behaviors: what happens if the username already exists, and that non-idempotent retries could produce duplicates.

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?

Three short sentences, front-loaded with the action and followed by the safety check; nothing is buried. The 'This changes RadiusStack' clause is mildly redundant against the readOnlyHint=false annotation, costing a point.

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?

For a 7-parameter mutation with no output schema, the description should state the duplicate-username behavior and whether any record is returned. It covers the safety confirmation but leaves those operational gaps for an agent invoking a non-idempotent write.

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 86%, so nearly every parameter is already documented in the schema (username, password, planId, profile, staticIp, disabled, totpEnabled). The description adds no meaning beyond that baseline, which is the expected floor here.

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 opens with a specific verb+resource ('Create a RADIUS user'), which cleanly separates it from siblings like radiusstack_update_user and radiusstack_list_users. It does not explicitly name those siblings, so it stops short of a 5.

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?

It gives a precondition ('Confirm the requested username and settings before calling') but no guidance on when to prefer this over radiusstack_update_user for an existing account, nor any prerequisites such as plan availability. Usage is only implied by the create semantics.

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