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

FengSui 4G/5G Router MCP Server

Clear Band and Cell Locks

unlock_rf_locks
DestructiveIdempotent

Remove all 4G/5G band, channel, and cell locks so the router can select bands and cells automatically again; the mobile connection may briefly drop while it reattaches.

Instructions

Remove every 4G and 5G band, channel and cell lock, so the router chooses bands and cells on its own again. It may drop the mobile connection for a moment while it attaches again. Use it to undo lock_band or lock_cell; get_cpe_telemetry shows the locks in force.

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

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

A4.7/5.0
Behavior5/5

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

The annotations already declare this as destructive and idempotent, but the description adds important context: it removes every band, channel, and cell lock, and may briefly drop the mobile connection while the router reattaches. That is behavior beyond the annotation flags.

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?

The description is two compact sentences, front-loads the action and scope, then adds the side effect and usage guidance. Every sentence contributes relevant information without redundancy.

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 lock-clearing operation with no output schema, the description covers what is removed, the temporary connectivity impact, when to use it, and where to inspect current locks. Nothing essential for correct invocation appears to be missing.

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 description coverage is 100%, and the single parameter confirm is fully documented in the schema as requiring an explicit user request. The description does not add meaning beyond that schema information, so the baseline 3 applies.

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?

The description uses a specific verb and resource: 'Remove every 4G and 5G band, channel and cell lock.' It states the resulting scope ('router chooses bands and cells on its own again') and distinguishes the tool from related operations by naming lock_band and lock_cell.

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?

It explicitly says to use this tool to undo lock_band or lock_cell, and points to get_cpe_telemetry for checking which locks are in force. This gives clear when-to-use guidance and names the relevant alternatives for inspection.

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