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

FengSui 4G/5G Router MCP Server

Lock a 4G or 5G Cell

lock_cell
DestructiveIdempotent

Locks a router to a chosen 4G LTE or 5G NR cell by ARFCN and optional PCI, or to a channel alone, keeping it on a known cell. Find valid values with list_neighbor_cells; unlock_rf_locks clears it.

Instructions

Lock the router to one 4G (LTE) or 5G (NR) cell, given by its channel number (ARFCN) and PCI, or to a channel alone when pci is left out. Only cells FengSui has seen can be locked (the serving cell, an aggregated carrier or one from the latest neighbour list): call list_neighbor_cells first and copy rat, band, arfcn and pci from its result. A cell that cannot serve the router takes it offline; unlock_rf_locks removes the lock.

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": {
      "rat": "<rat>",
      "band": "<band>",
      "arfcn": "<arfcn>",
      "confirm": "<confirm>"
    },
    "name": "lock_cell"
  }
}

Input Schema

NameRequiredDescriptionDefault
pciNoThe cell's Physical Cell ID (4G 0 to 503, 5G 0 to 1007). Leave it out to lock the channel only.
ratYes'LTE' for a 4G cell, 'NR' for a 5G cell.
bandYesThe cell's band, as a label or a number (e.g. 'B1' or 'N78').
moreNoOptional further candidate cells of the same RAT, each observed like the first: the router picks among them. Only routers that lock several cells at once take them (an OpenWrt router with a Quectel module, 4G; a FiberHome LG6151M); any other refuses them before anything is sent. The first cell then needs its pci.
arfcnYesThe cell's downlink channel number (EARFCN for 4G, NR-ARFCN for 5G), as list_neighbor_cells gives it.
confirmYesMust be true: the user explicitly asked for this change.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.9.5

TDQS

A4.9/5.0
Behavior5/5

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

Goes well beyond the destructiveHint/idempotentHint annotations by disclosing the concrete failure mode: a cell that cannot serve the router takes it offline. It also explains that the multi-cell `more` parameter is rejected by unsupported routers 'before anything is sent', which pre-empts a confusing error path.

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 sentences with no filler, ordered as action, prerequisite, risk/recovery. The core verb and resource lead the first sentence before any caveats.

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

Completeness5/5

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

For a destructive, mutation-style tool with no output schema and six parameters, the definition covers prerequisites, hardware-specific limits, irreversible risk, and the recovery path. Nothing an agent needs in order to call it safely is missing.

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?

Schema coverage is 100%, so the baseline is 3; the description nonetheless adds provenance ('as list_neighbor_cells gives it') and reiterates the pci-omitted semantics and the constraint that `more` is accepted only on specific router models. Most of the remaining per-field meaning still lives in the schema descriptions, so it is not a full 5.

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?

States a specific verb and resource ('Lock the router to one 4G (LTE) or 5G (NR) cell') and immediately identifies the identifying keys (ARFCN and PCI). It also distinguishes the variant behavior (channel-only lock when pci is omitted), which no sibling tool would claim.

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 sequencing ('call list_neighbor_cells first and copy rat, band, arfcn and pci from its result') and a precondition restricting the candidate set to cells FengSui has observed. It names the escape hatch ('unlock_rf_locks removes the lock') so the agent knows the alternative for reversing the operation.

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