mcp-remnawave

users_bulk_all_extend_expiration

Extend expiration date for all users in a Remnawave VPN panel by specifying the number of days to add.

Instructions

Extend expiration date for ALL users

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": {
      "days": "<days>"
    },
    "name": "users_bulk_all_extend_expiration"
  }
}

Input Schema

Name	Required	Description	Default
`days`	Yes	Number of days to extend

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.1.0Sep 10, 2026

TDQS

B3.3/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 clearly indicates a bulk mutation, but it does not disclose potential side effects, irreversibility, scope boundaries (e.g., whether disabled or deleted users are included), or any confirmation requirements. For an operation affecting all users, this is a significant transparency gap.

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?

The description is a single, front-loaded sentence with no filler. It communicates the core action and scope efficiently, though more behavioral context would be warranted for a bulk-all mutation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a broad, potentially impactful operation with one parameter, no output schema, and no annotations. The description is too minimal: it fails to clarify what 'ALL users' means in practice, whether the extension is additive, and what safeguards or limitations apply. An agent needs more context to safely invoke this tool correctly.

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?

The schema already fully documents the single 'days' parameter with a description and a minimum value, so schema coverage is 100%. The tool description adds no additional meaning about how 'days' interacts with expiration, which is acceptable because the schema carries the parameter semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('extend'), a clear resource ('expiration date'), and the exact scope ('ALL users'). This distinguishes it from sibling tools like users_bulk_extend_expiration and users_extend_expiration, which presumably target selected or single users.

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 phrase 'ALL users' implies the use case: this tool is for extending expiration dates across the entire user base, not for individual or selected users. However, it does not explicitly name any alternative tools or state when not to use it, leaving the routing mostly to inference.

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

Deploy Server