Skip to main content
Glama
RadiusStack MCP Server

RadiusStack MCP Server

by deangoldhill

Get RadiusStack user statistics

radiusstack_get_user_stats
Read-onlyIdempotent

Retrieve usage and authentication statistics for a single RadiusStack user by username to monitor account activity and access trends.

Instructions

Read usage and authentication statistics for one RadiusStack 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": {
      "username": "<username>"
    },
    "name": "radiusstack_get_user_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
usernameYesRadiusStack username

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, and non-destructive, so the safety profile is covered without description help. The description adds only the data domain (usage + authentication stats) and per-user scoping; it says nothing about time window, aggregation, or whether missing users error or return empty.

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 filler or redundancy. It is efficient, though the brevity leaves little room for the qualifying context the tool would benefit from.

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?

The tool is simple: one required string parameter, no nesting, no output schema, and annotations that fully cover the safety profile. Given that low complexity, the description is nearly sufficient, with the main residual gap being what the returned statistics actually encompass (time range, metric set).

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?

There is a single required parameter with 100% schema description coverage, so the schema already defines "username" (type, length bounds, meaning). The description adds no format, case-sensitivity, or identifier-resolution details beyond what the schema provides, which is the expected baseline 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?

States a specific verb ("Read") and resource ("usage and authentication statistics") scoped to "one RadiusStack user", which distinguishes it from the aggregate/live-stats sibling by scope. It does not name the sibling explicitly, so an agent must infer the per-user vs. live distinction rather than being told.

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: "for one RadiusStack user" suggests this is the per-user lookup versus live/aggregate statistics, but there is no explicit when-to-use, when-not-to-use, or named alternative (e.g., radiusstack_get_live_stats). The agent must derive the routing decision from the scope phrase alone.

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