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

FengSui 4G/5G Router MCP Server

Mark SMS as Read

mark_sms_read
Idempotent

Mark SMS messages by UID or an entire conversation thread as read on the router. Requires explicit confirmation to apply the read status change.

Instructions

Mark messages (by uid) or a whole conversation (threadKey) as read on the router. Requires confirm: true.

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

Input Schema

NameRequiredDescriptionDefault
uidsNoThe messages to mark, by the uid get_sms_thread gives each; at most 50.
confirmYesMust be true: the user explicitly asked for this change.
threadKeyNoInstead of uids: a whole conversation, by the threadKey list_sms_threads gives it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.9.5

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the mutation/repeat-safety profile is covered structurally. The description adds that the change is applied on the router and that confirmation is mandatory, but says nothing about what happens to already-read messages, whether the change affects server-side state, or partial-failure behavior for a 50-item batch.

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 short sentences with zero filler; the two targeting modes are front-loaded and the hard prerequisite follows immediately. Nothing is repeated needlessly and nothing is buried.

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 three-parameter mutation with full schema descriptions and annotations covering the safety profile, the description covers both invocation paths and the confirmation gate. The only omissions are return behavior and batch edge cases, which are minor given the tool's simplicity and the absence of an output schema.

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%, so all three parameters are already documented, including value provenance from get_sms_thread and list_sms_threads. The description reinforces the mutually exclusive modes with 'or' but adds no format, limit, or edge-case detail beyond the schema. 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?

States a specific verb and resource ('Mark ... as read') and enumerates the two targeting modes (uid list vs. threadKey). An agent can distinguish it from delete_sms or get_sms_thread without opening the schema. It does not explicitly contrast with sibling tools, which keeps it at 4 rather than 5.

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

Usage Guidelines3/5

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

The description supplies the key gating condition ('Requires confirm: true'), which is the main when-to-use signal for this mutation. It gives no guidance on choosing between the uids and threadKey modes beyond a bare 'or', and no context on when to prefer this over other SMS operations. Minimum viable guidance.

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