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

FengSui 4G/5G Router MCP Server

Check FengSui's Session With the Router

get_cpe_session_status
Read-onlyIdempotent

Checks if someone is signed in to the router web page, tracks FengSui's last admin session, reports an open login breaker, and shows WAN self-healing lock rollback and redial status.

Instructions

Check whether a person is signed in to the router's own web page (FengSui then steps aside), how long FengSui's last session held the router's admin seat, whether the breaker is open (the router refused the password or locked its login, so FengSui stopped signing in), and what WAN self-healing does on its own (selfHeal: whether a lock is rolled back when the WAN is still down lockRollback.afterMin minutes later, an open lock window's deadline, and the WAN redials spent of the 24 h cap).

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

Input Schema

NameRequiredDescriptionDefault
probeLiveNoAlso ask the router right now, without a login, whether someone is signed in (Huawei routers only; on another brand the tool answers VALIDATION_ERROR).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, and the description adds substantial context beyond that: breaker semantics (router refused password or locked login, so FengSui stops signing in), self-heal lock rollback after lockRollback.afterMin, an open lock window's deadline, and a 24 h redial cap. The jargon is dense but genuinely discloses behavior an agent could not get from the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The main purpose is front-loaded, but the whole definition is one sprawling sentence with nested parentheticals that make the four reported facets hard to scan. The content earns its place, yet the structure would benefit from breaking the facets into separate clauses or a list.

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 read-only status tool with no output schema, the description covers the meaningful return facets (sign-in state, session duration, breaker, self-heal/redial limits) and the brand-specific caveat. It stops short of describing the actual response shape, which is acceptable given no output schema exists.

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% for the single probeLive parameter, which already documents that it queries the router without a login and errors with VALIDATION_ERROR on non-Huawei brands. The description adds no parameter detail, so baseline 3 applies.

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?

The description names a clear verb ('Check') and enumerates the specific facets reported: sign-in state on the router's own page, FengSui's last admin-session duration, breaker state, and WAN self-healing behavior. It is distinct enough from siblings like get_router_settings or get_cpe_telemetry, though it never explicitly contrasts itself with them.

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

Usage Guidelines2/5

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

There is no when-to-use, when-not-to-use, or alternative guidance. The description explains what data is returned but leaves the agent to infer when this status check is the right call versus get_router_settings or get_cpe_telemetry; the only conditional guidance is the brand caveat embedded in the parameter schema.

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