Skip to main content
Glama
Sign In
mcp-remnawave

mcp-remnawave

by Nurullaev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

system_stats_digest

Retrieve a digest of system statistics for any date-time range to monitor VPN panel performance and resource usage.

Instructions

Get system statistics digest for a date-time range

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": {
      "start": "<start>",
      "end": "<end>"
    },
    "name": "system_stats_digest"
  }
}

Input Schema

NameRequiredDescriptionDefault
endYesEnd date-time (ISO 8601)
startYesStart date-time (ISO 8601, e.g. 2026-08-01T00:00:00Z)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states that a digest is returned for a date-time range; it does not disclose whether the operation is read-only, what the digest contains, how aggregation works, or what response shape to expect.

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?

The description is a single, tight sentence with no filler words. It front-loads the action and resource, and every word contributes to the core meaning.

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?

The tool is simple and both required parameters are fully documented, so invocation is straightforward. However, with no output schema, no annotations, and multiple similar system_* siblings, the description leaves ambiguity about what a 'digest' contains and how it differs from other statistics tools.

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%: both start and end parameters are documented with ISO 8601 descriptions and an example. The description adds nothing beyond restating 'date-time range', so the schema carries the parameter semantic weight. Baseline 3 is appropriate.

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 states a specific verb ('Get'), a resource ('system statistics digest'), and a time range constraint. However, it does not explicitly distinguish the digest from closely named siblings like system_stats, system_stats_http, and system_stats_recap.

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 guidance about when to use this tool versus the many other system_* statistics tools. The description only states what the tool does, with no exclusions, alternatives, or context to help an agent choose correctly among similar siblings.

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

Deploy Server

Other Tools