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

FengSui 4G/5G Router MCP Server

List Nearby 4G and 5G Cells

list_neighbor_cells
Read-onlyIdempotent

Lists nearby 4G/5G cells the router can hear, including band, channel, PCI and signal, so you can choose and copy valid values before locking a cell.

Instructions

List the 4G (LTE) and 5G (NR) cells the router can hear besides the one it uses: each cell's band, channel number (EARFCN or NR-ARFCN), PCI and signal (RSRP, RSRQ, RSSI, SINR, as far as the router reports them). Use it before locking a cell: only cells listed here or currently in use can be locked, with their values copied from this result.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_neighbor_cells"
  }
}

Input Schema

NameRequiredDescriptionDefault
scanNowNotrue: ask the router for a new scan now. false: the last scan only (none yet gives null). Omitted: a new scan only when there is no earlier one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.9.5
    • changedInput schema / properties / scanNow / description
      Previous value: -"Trigger an immediate ephemeral neighbor scan (default true if cache empty)."New value: +"true: ask the router for a new scan now. false: the last scan only (none yet gives null). Omitted: a new scan only when there is no earlier one."
  2. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive, so the safety profile is settled. The description adds useful behavior beyond that: results are partial ('as far as the router reports them') and act as a source of truth for a subsequent lock operation. It does not describe scan latency or ordering, hence not a 5.

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 sentences, front-loaded with purpose and followed by the actionable constraint. No boilerplate and nothing redundant with the schema.

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?

There is no output schema, and the description compensates by naming the fields returned (band, EARFCN/NR-ARFCN, PCI, RSRP, RSRQ, RSSI, SINR) and flagging that data may be partial. An agent has everything needed to call it and use the result.

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 scanNow parameter is fully documented in the schema, so the baseline of 3 applies. The description adds no meaning about scanNow (e.g., cost or freshness tradeoffs) beyond what the schema already states.

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 ('List the 4G (LTE) and 5G (NR) cells') with explicit scope ('besides the one it uses') and enumerates the returned fields. It also distinguishes itself from the sibling lock_cell by framing this as the prerequisite read step.

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?

Gives a concrete when-to-use rule ('Use it before locking a cell') plus the constraint that only listed or in-use cells can be locked, and that values must be copied from this result. No explicit when-not or naming of a competing read tool, so it falls short of the 5 bar.

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