Skip to main content
Glama
RadiusStack MCP Server

RadiusStack MCP Server

by deangoldhill

Update RadiusStack user

radiusstack_update_user

Update selected RadiusStack user settings, including plan, profile, password, static IP, TOTP, and disabled status. Confirm intended changes before calling, as it modifies live user data.

Instructions

Update selected RadiusStack user settings. This changes RadiusStack. Confirm changes 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>"
    },
    "name": "radiusstack_update_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
planIdNoOptional RadiusStack plan ID.
profileNoOptional RadiusStack profile name.
disabledNoWhether RadiusStack should reject authentication for this user.
passwordNoCleartext RADIUS password. It is sent only to RadiusStack and is never returned.
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, destructiveHint=false and idempotentHint=false, so the description's 'This changes RadiusStack' is largely redundant restatement. The one piece of added value is the confirmation requirement before invoking a mutation; it does not address partial-update semantics (are omitted fields left intact?) or any permission requirements, which matters given idempotentHint=false.

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 verb and resource. The middle sentence ('This changes RadiusStack.') is near-vacuous filler that restates the tool name, costing a point, but nothing else is padded.

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 tool with no output schema, the definition is thin: it omits update semantics, permission needs, and whether the response reflects applied changes. Annotations carry the safety profile and the schema carries parameter detail, which keeps this at minimum-viable rather than inadequate.

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 every parameter is already documented in the schema, including password handling and disabled semantics. The description's phrase 'selected settings' hints at partial update but never clarifies whether unspecified fields are preserved or cleared, so it adds only marginal meaning over the schema.

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 and resource: 'Update selected RadiusStack user settings.' That is unambiguous enough to separate it from radiusstack_create_user and the read-only siblings, though it never names those siblings or states the discrimination explicitly.

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 only guidance is 'Confirm changes before calling,' which is a procedural caution rather than a when-to-use rule. It implies use on an existing user (the required username), but gives no exclusions, prerequisites, or alternatives such as create vs update.

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