Skip to main content
Glama
iKuai MCP Server
by gxxHuang

Scan Nearby Signals

scan_nearby_signals
Read-only

Scan nearby wireless signals to retrieve BSSID and signal strength details, helping you diagnose interference and adjust iKuai router Wi-Fi settings.

Instructions

扫描周边无线信号详情(含 BSSID/信号强度)

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

B3.3/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read. The description adds that the payload includes BSSID and signal strength, which is useful context, but says nothing about latency (wireless scanning is slow), result volume, or whether the scan is live vs cached. An output schema exists, so return detail is partly redundant.

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?

A single front-loaded sentence with no filler, and the parenthetical scoping the result fields is the most information-dense part. Slightly terse given it must stand alone against several lookalike scan siblings.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-arg read tool with an output schema and a readOnlyHint, the core facts are covered. What is missing is sibling disambiguation and any note on scan duration or freshness, which is the main thing an agent needs before firing a wireless scan.

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 for the description to disambiguate; baseline 4 applies. Schema coverage is 100% but vacuous since the object has no properties.

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 gives a specific verb (扫描) and resource (周边无线信号) and even names what the result contains (BSSID/信号强度), so the agent knows what it gets. However it does not differentiate from the nearby sibling scan_surrounding_channels / start_channel_scan, which are visually indistinguishable scan operations in the same list.

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

Usage Guidelines2/5

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

There is no guidance on when to use this versus scan_surrounding_channels, start_channel_scan, or get_wireless_monitoring, all of which sit adjacent in the sibling list. Usage is only implied by the verb 'scan'.

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

Deploy Server

Other Tools