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

FengSui 4G/5G Router MCP Server

Allow or Stop Data Roaming

set_data_roaming
DestructiveIdempotent

Controls mobile data use while roaming, enabling it when connectivity abroad is needed or disabling it to avoid roaming fees.

Instructions

Set whether the router uses mobile data while roaming (abroad, or on another operator's network). Allowing it may cost roaming fees; stopping it leaves the router without internet while it roams. get_cellular_settings shows the current setting.

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": {
      "enabled": "<enabled>",
      "confirm": "<confirm>"
    },
    "name": "set_data_roaming"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesMust be true: the user explicitly asked for this change.
enabledYestrue allows mobile data while roaming, false stops it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.9.5

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true; the description adds the concrete real-world impact that makes 'destructive' meaningful here (roaming charges, loss of connectivity abroad). It does not restate that the confirm flag must be user-authorized, but that requirement is fully documented in the schema.

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 compact sentences: the operation first, then the cost/connectivity consequences, then the pointer to the read tool. Every clause carries information an agent needs before invoking a billable mutation.

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 two-parameter toggle with no output schema, the description supplies purpose, both outcome branches, and the companion read tool, which is enough to call it correctly. Only a more explicit note on the confirmation gate or the response shape would round it out.

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 description coverage is 100%, so both parameters are already self-documenting. The description restates the meaning of 'enabled' in prose but adds no format, default, or edge-case detail beyond what the schema provides, making the baseline 3 appropriate.

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?

States a specific verb and resource with scope: 'Set whether the router uses mobile data while roaming (abroad, or on another operator's network).' The parenthetical removes ambiguity about what roaming means, and naming get_cellular_settings separates the write tool from its read counterpart.

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?

Gives clear decision context by spelling out the consequence of each branch — fees when allowing, loss of internet while roaming when stopping — and routes the agent to get_cellular_settings to inspect the current value. It stops short of explicitly contrasting with set_mobile_data, so the agent must infer the boundary between general mobile data and roaming data.

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