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

FengSui 4G/5G Router MCP Server

Get SMS Storage and Sync Status

get_sms_status
Read-onlyIdempotent

Check router SMS storage levels: unread, inbox, outbox counts and capacity, plus encrypted-copy counts, last sync time, and pending changes to spot a filling inbox without reading message text.

Instructions

Return the router's SMS counters (unread, inbox and outbox, how many it can hold), how many messages FengSui's encrypted copy holds, when it last synced with the router, and changes still waiting to reach the router. Use it to see whether the router's SMS storage is filling up. Reads no message text.

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_sms_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuine value beyond that with 'Reads no message text,' which tells the agent the payload is metadata-only and privacy-safe. However, it says nothing about how the pending-change count relates to sync_sms, or about freshness/staleness of the last-synced timestamp.

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 the return contents and closed with the storage-filling use case plus the no-message-text caveat. Every clause carries information and nothing is repeated from the schema or annotations.

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?

With no parameters and no output schema, the description itself must describe what comes back, and it does so field by field, including the sync timestamp and pending-change count. An agent can call this tool and interpret the result without further documentation.

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?

The tool takes zero parameters, so there is nothing to disambiguate and the baseline of 4 applies. The description puts its effort where it matters instead, spelling out the shape of the returned counters.

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 opens with a specific verb+resource ('Return the router's SMS counters') and enumerates the exact fields returned: unread, inbox, outbox, capacity, encrypted-copy count, last sync time, and pending changes. It implicitly separates itself from message-reading siblings via the storage-counter framing, but never names get_sms_thread or sync_sms to make the distinction explicit.

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?

It gives a clear primary use case: 'Use it to see whether the router's SMS storage is filling up.' That is a concrete condition for selecting this tool. It stops short of stating when not to use it or pointing at sync_sms for actually triggering a sync, so no explicit alternatives are offered.

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