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

FengSui 4G/5G Router MCP Server

Sync SMS From the Router

sync_sms
Read-onlyIdempotent

Reads router SMS messages into FengSui's encrypted copy on demand and returns added, updated, and removed changes, without altering messages on the router.

Instructions

Read the router's messages into FengSui's encrypted copy now, instead of waiting for the next automatic sync, and return what changed (added, updated, removed). Runs in FengSui's own short session with the router, which steps aside when someone is signed in to the router's own web page. Changes no message on the router.

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

Input Schema

NameRequiredDescriptionDefault
modeNo'full' (default) reads every message; 'incremental' only what is new since the last sync.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.9.5
    • changedInput schema / properties / mode / description
      Previous value: -"Default 'full'."New value: +"'full' (default) reads every message; 'incremental' only what is new since the last sync."
  2. First observedv0.1.0

TDQS

A4.1/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses the short dedicated session, the contention rule with a signed-in router web page, the fact that it writes nothing on the router, and the shape of the result (added/updated/removed). The read-only annotation is consistent with 'Changes no message on the router'.

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?

One dense sentence with the action and its timing benefit front-loaded, followed by two short supporting clauses. Efficient, though the embedded parenthetical result list slightly burdens the main sentence.

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 single-optional-parameter tool with no output schema, the description covers purpose, timing, session contention, mutation safety, and return shape. Nothing an agent needs in order to call it correctly is 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 coverage is 100% and the single 'mode' enum is fully documented in the schema itself. The description never mentions 'full' vs 'incremental', so it adds no meaning here, but the baseline 3 applies because the schema carries it.

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?

States a concrete verb and resource ('Read the router's messages into FengSui's encrypted copy') plus the effect ('return what changed'). It distinguishes itself from the automatic sync path, but never contrasts with the read-style siblings like get_sms_thread or list_sms_threads, so an agent must infer that boundary.

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?

Explicitly frames the when: use it 'now, instead of waiting for the next automatic sync'. It also gives a real operating condition (the router's own web session takes precedence). No when-not or named alternative tool is given, so it stops short of a 5.

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