Skip to main content
Glama
RadiusStack MCP Server

RadiusStack MCP Server

by deangoldhill

Get RadiusStack live statistics

radiusstack_get_live_stats
Read-onlyIdempotent

Read current RadiusStack live statistics to monitor system activity and support reporting. Requires reports read permission.

Instructions

Read current RadiusStack live statistics. Requires reports read permission.

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_get_live_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds a genuinely useful auth requirement ('Requires reports read permission') but says nothing about what 'live' means (real-time vs cached, any time window) or about rate limits.

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 action front-loaded and no filler. Every clause carries information, and the permission requirement follows the purpose rather than burying it.

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 zero-parameter read tool the definition is nearly sufficient, and annotations cover the safety profile. However, there is no output schema, so the description should have hinted at what the returned statistics include; 'live statistics' leaves the agent guessing at the response shape.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter semantics for the description to explain; the baseline of 4 applies. The schema is also fully described and empty, so nothing is missing on this dimension.

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 gives a specific verb ('Read') and resource ('current RadiusStack live statistics'), so the agent knows this is a read-only stats fetch rather than a user mutation. It never states what 'live statistics' actually contains or how it differs from radiusstack_get_user_stats, so differentiation rests mostly on the name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance and no mention of when not to use it or which sibling to pick for user-scoped data. The only condition given is a permission prerequisite, which is a precondition rather than selection guidance.

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