Skip to main content
Glama
RadiusStack MCP Server

RadiusStack MCP Server

by deangoldhill

List RadiusStack users

radiusstack_list_users
Read-onlyIdempotent

Retrieve paginated RadiusStack user records with password fields removed, and filter by username, profile, plan, or search text.

Instructions

List RadiusStack users. Password fields are removed before results are returned.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "radiusstack_list_users"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, starting at 1.
searchNoOptional username, profile, plan, or password search text.
pageSizeNoUsers per page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context by disclosing that password fields are stripped before results are returned, which is security-relevant and not derivable from the annotations. It stops short of describing result shape, ordering, or paging behavior.

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 zero filler, and the identity of the tool is front-loaded before the redaction note. Nothing could be removed without losing information.

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 simple read-only list endpoint with full schema documentation and no output schema, this is largely sufficient: paging is covered by the schema and the redaction caveat is stated. Minor gaps remain around default page size, result ordering, and what fields are actually returned.

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% and all three parameters (page, search, pageSize) are documented in the schema, including pageSize's allowed values. The description adds no meaning beyond that, so the baseline of 3 applies.

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 ("List RadiusStack users"), which cleanly separates it from the create/update/get_stats siblings. It does not explicitly name those siblings, but the list-versus-mutate distinction is unambiguous 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 "List" signals a browse/enumerate operation, and nothing states when to prefer this over radiusstack_get_user_stats or radiusstack_update_user. No exclusions, prerequisites, or pagination guidance are offered.

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