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

FengSui 4G/5G Router MCP Server

Preview an SMS Before Sending

preview_sms
Read-onlyIdempotent

Checks an SMS recipient and message before sending: resolves the number to E.164, calculates encoding and segment count, and reports whether server policy would accept it without sending anything.

Instructions

Resolve the recipient to E.164, compute GSM-7/UCS-2 encoding and segment count, and report whether send_sms would accept this recipient under the server's policy. Sends nothing.

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": {
      "phone": "<phone>",
      "content": "<content>"
    },
    "name": "preview_sms"
  }
}

Input Schema

NameRequiredDescriptionDefault
phoneYesThe recipient's number, international (+353…) or national with countryCode.
contentYesThe message text to check.
countryCodeNoDial code for a national number, e.g. '+353' (default: the one FengSui is set to).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.9.5
    • addedInput schema / properties / content / description
      Added value: +"The message text to check."
    • changedInput schema / properties / countryCode / description
      Previous value: -"Dial code for national numbers, e.g. '+353'."New value: +"Dial code for a national number, e.g. '+353' (default: the one FengSui is set to)."
    • addedInput schema / properties / phone / description
      Added value: +"The recipient's number, international (+353…) or national with countryCode."
  2. First observedv0.1.0

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, and the description reinforces that with 'Sends nothing' while adding real behavioral detail about E.164 normalization and encoding/segment computation. It does not say what happens on an unresolvable number, whether a policy rejection is an error or a returned verdict, or how results are surfaced, which for a validation tool with no output schema is a meaningful remaining gap.

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?

A single tightly packed sentence with the three computed outputs listed in order and the most important guarantee ('Sends nothing') front-loaded at the end as a short, high-salience clause. No filler or restated field names.

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 output schema present, the description takes on the burden of describing returns and does so by naming the resolved E.164 value, the encoding, the segment count, and the policy verdict. Combined with complete schema coverage on all three parameters and annotations covering the safety profile, an agent has everything needed to call it correctly.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning by explaining what happens to the inputs: phone is normalized to E.164 and content is analyzed for GSM-7/UCS-2 encoding and segment count. The countryCode fallback is left entirely to the schema, which is acceptable given its documented default.

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?

The description names a specific multi-part verb set (resolve to E.164, compute GSM-7/UCS-2 encoding and segment count, report policy acceptance) and explicitly positions itself relative to the sibling send_sms. The closing 'Sends nothing' pins down what it is not, so an agent can distinguish it from send_sms without opening either schema.

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?

The pre-send framing and the reference to whether send_sms 'would accept this recipient under the server's policy' make the intended use case clear: validate before committing a send. It stops short of an explicit 'use this instead of send_sms when you only want to validate' statement or any exclusion, but the context for choosing it is unambiguous.

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