Retrieve all subscriptions from a Remnawave panel with pagination controls for start index and result size.
Get all subscriptions [READ] GET /api/subscriptions/
| Name | Required | Description | Default |
|---|---|---|---|
| size | No | Number of subscriptions to return, no more than 500 | |
| start | No | Start index (offset) of the users to return, default is 0 |
Changes observed during successful MCP inspections.
v1.1.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that — the "[READ] GET /api/subscriptions/" tag merely restates the read-only annotation and offers no detail on pagination behavior, result envelope, or access requirements.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Very short and front-loaded, with the core action stated first. The bracketed endpoint tag is arguably redundant noise but does not bloat the definition.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema, the description carries the burden of conveying what is returned, yet it says nothing about the response shape or pagination envelope. For a list tool with sibling overlap, it is under-specified.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, with both the size and start parameters fully documented in the schema, so the baseline of 3 applies. The description adds no extra meaning about pagination or ordering beyond what the schema already provides.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource ("Get all subscriptions"), and the word "all" signals a bulk-list operation as opposed to the many single-subscription siblings like get_subscription_by_id or get_subscription_by_username. It does not, however, explicitly name or differentiate itself from those siblings.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no statement of when to use this tool versus the numerous subscription-related alternatives (get_subscription_by_id, get_subscription_by_username, get_subscription_settings, etc.). The agent must infer from the name alone that this is the list-all variant.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.