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

FengSui 4G/5G Router MCP Server

Create, Update or Delete an Internet Time Rule

manage_internet_time_rule
Destructive

Create, update or delete a parental-control rule that limits one device to allowed online windows on chosen weekdays, blocking it outside those times.

Instructions

Create, change or delete an internet time rule (parental control). A rule is an ALLOWED online window for one device on chosen weekdays: once a device has rules, it is cut off outside all of its windows. Times are HH:mm in 15-minute steps; an end before the start runs past midnight. get_access_control lists the rules and their ids.

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

Input Schema

NameRequiredDescriptionDefault
idNoThe rule's id, as get_access_control lists it (update and delete only).
actionYes'create' a rule, 'update' or 'delete' the one with id.
confirmYesMust be true: the user explicitly asked for this change.
enabledNofalse keeps the rule but stops applying it.
endTimeNoWhen it closes, HH:mm in 15-minute steps; earlier than startTime runs past midnight.
weekMaskNoSeven 0s and 1s for the days the window applies, Monday first: 1111100 is Monday to Friday.
startTimeNoWhen the allowed window opens, HH:mm in 15-minute steps.
macAddressNoThe device's MAC address (AA:BB:CC:DD:EE:FF), as list_terminal_topology gives it.
ipv4AddressNoInstead of macAddress: the device's LAN IPv4 address, as list_terminal_topology gives it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.9.5

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and non-idempotent, and the description adds genuine behavioral context beyond them: the cutoff consequence ('once a device has rules, it is cut off outside all of its windows'), the 15-minute granularity, and the past-midnight semantics. It does not state whether 'update' merges unspecified fields or replaces the whole rule, which is the main behavioral gap.

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?

Three tight sentences, front-loaded with the action, then the domain model, then the time format and the id source. No filler and no restatement of the tool name.

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 9-parameter destructive mutation with no output schema, the description supplies the semantic model and format constraints an agent needs. Residual gaps are update/delete semantics (merge vs. replace, what happens to rules on delete) and the exact meaning of the confirm requirement, which lives only in the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although schema coverage is 100% (baseline 3), the description goes beyond it: the ALLOWED-window model gives meaning to startTime/endTime/weekMask together, the 'end before start runs past midnight' rule and the 15-minute step constraint tie the time parameters to their valid domain, and get_access_control is named as the source of ids.

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?

Opens with a specific verb triad and resource ('Create, change or delete an internet time rule (parental control)'), then defines what a rule actually is. An agent can tell this apart from read-only siblings like get_access_control purely from the description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explains the two-step workflow: use this tool to mutate rules, and get_access_control to list rules and their ids. It states the mode of operation clearly but never carves out when to prefer a different access tool (e.g. device-level internet access controls) or what to do if the id is unknown apart from the pointer.

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