Skip to main content
Glama
Sign In
mcp-remnawave

mcp-remnawave

by Nurullaev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

node_plugins_torrent_reports

Retrieve torrent blocker reports to identify nodes where torrent traffic has been blocked. Use this tool to audit blocked torrent attempts and enforce network policies.

Instructions

Get torrent blocker reports

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": "node_plugins_torrent_reports"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

With no annotations, the description carries the full burden of behavioral disclosure. 'Get' implies a read-only operation, but the description does not reveal what a 'torrent blocker report' contains, whether it is per-node or global, or any side effects. This is a minimal but not misleading description; it simply lacks detail.

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?

A single clear sentence with the verb front-loaded. There is zero redundancy or filler. For a tool with no parameters and a simple read operation, this is appropriately sized.

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?

Although the tool is simple (0 params), there is no output schema and no annotations. The description does not explain what the returned 'torrent blocker reports' look like, what data they cover, or whether they are scoped to a node. An agent would need additional context to interpret the result confidently.

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 input schema is empty, so the schema fully documents that this tool takes no parameters. The description adds the resource context ('torrent blocker reports') and confirms there is no filtering or options. With zero parameters, the baseline is 4, and the description does not detract from that.

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 'Get torrent blocker reports' uses a specific verb ('Get') and a specific resource ('torrent blocker reports'), which is clear on its own. It distinguishes from siblings by naming a distinct resource type ('reports' vs 'stats' or 'truncate'), though it does not explicitly call out the alternative.

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 on when to use this tool versus alternatives such as node_plugins_torrent_stats or node_plugins_torrent_truncate. The description does not state any context, prerequisites, or exclusions, so an agent must infer usage from the name alone.

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