Skip to main content
Glama
FengSui 4G/5G Router MCP Server

FengSui 4G/5G Router MCP Server

Clear the Router's Traffic Counters

reset_traffic_counters
DestructiveIdempotent

Permanently clears the router's monthly and total traffic counters after explicit confirmation; this action cannot be undone.

Instructions

Clear the traffic counters the router itself keeps (this month's and the totals). They cannot be brought back.

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": {
      "confirm": "<confirm>"
    },
    "name": "reset_traffic_counters"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesMust be true: the user explicitly asked for this change.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.9.5

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare destructiveHint=true and idempotentHint=true, so the description goes beyond structured data by specifying the blast radius: the router's own counters, both this month's and the totals, and that the values are unrecoverable. It does not say whether the reset takes effect immediately or whether more than one counter is zeroed (for example, per-interface counters); it only paraphrases the destructive hint.

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, zero filler, with the scope (which counters) front-loaded and the irreversibility caveat second. Nothing could be removed without losing information.

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

Completeness4/5

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

For a one-parameter destructive reset with no output schema, the definition covers the safe amount: what is destroyed, that it is irreversible, and that the annotations carry the safety profile while the schema carries the confirmation guard. The only minor gap is timing and granularity of the reset, which is not essential for correct invocation.

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?

There is a single parameter, and the schema already documents it fully (100% coverage) with a description explaining that it must be true only when the user explicitly asked for the change. The description adds nothing about confirm, so the baseline of 3 applies.

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 names a specific verb ("Clear") and resource ("the traffic counters the router itself keeps"), and it scopes the resource to the router's own month-to-date and total counters rather than per-client counters. It is clear enough to act on, though it never names a sibling or alternative, so there is no explicit differentiation in the text.

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 warning "They cannot be brought back" implies that this tool should only be used when the user truly wants the counters wiped, and the schema's confirm parameter reinforces that intent. But the description gives no explicit when-to-use, when-not-to-use, or alternative such as reading the counters first with a getter sibling; the usage context is only implied.

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