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

FengSui 4G/5G Router MCP Server

Lock 4G and 5G Bands

lock_band
DestructiveIdempotent

Lock a 4G/5G router to chosen LTE and NR bands, reject unsupported bands before sending, and clear per-generation locks with 'all'.

Instructions

Lock the router to the given 4G (LTE) and/or 5G (NR) bands, e.g. lteBands ['B1', 'B3'] and nrBands ['N78']; 'all' clears the lock for that kind, and a kind you leave out stays as it is. A band this router does not support is refused, with the bands it does, before anything is sent. Locking to bands no nearby cell uses takes the router offline: check get_cpe_telemetry and list_neighbor_cells first; unlock_rf_locks undoes the lock. If someone is signed in to the router's own web page, FengSui steps aside and sends nothing.

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

Input Schema

NameRequiredDescriptionDefault
confirmYesMust be true: the user explicitly asked for this change.
nrBandsNo5G bands to lock, e.g. ['N78'], or 'all' for every 5G band.
lteBandsNo4G bands to lock, e.g. ['B1', 'B3'], or 'all' for every 4G band.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.9.5

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the mutation profile is known; the description still adds substantial context beyond them. It discloses pre-flight validation ('a band this router does not support is refused, with the bands it does, before anything is sent'), the outage risk of locking to bands no nearby cell uses, and an unusual conditional where the router's web UI takes over and nothing is sent. It stops short of describing how the lock is applied or what happens to an in-flight connection, and the sign-in conflict is left without a retry or signalling instruction.

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?

Front-loaded with the core action and examples, then security/validation caveats in descending order of importance. It is a dense single block of semicolon-chained clauses that would scan faster as short sentences, but no clause is pure filler.

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 three-parameter mutating tool with no output schema, the definition covers preconditions, validation failure mode, and reversal, which is close to complete. It omits how the agent should proceed when the web-UI conflict blocks the call (retry, wait, or report to the user), leaving the failure path underspecified.

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?

Schema coverage is 100%, so the baseline applies. The description does add one genuinely new cue the schema lacks: an omitted kind stays unchanged, and 'all' clears rather than broadens, which contradicts the schema's wording that 'all' means 'every 5G band' in a locking sense. The band-name format is covered by both, so most of the text is redundant with the schema.

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?

Names a specific verb and resource (lock the router to given 4G/5G bands) with concrete examples ('lteBands ["B1", "B3"]', 'nrBands ["N78"]'). It does not explicitly differentiate itself from the sibling lock_cell, which also locks a radio target, so an agent must infer which one applies.

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

Usage Guidelines5/5

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

Gives explicit preconditions ('check get_cpe_telemetry and list_neighbor_cells first') and the reversal path ('unlock_rf_locks undoes the lock'). It also states that 'all' clears a lock rather than setting one, so the agent knows both the lock and unlock use cases route through this tool.

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