Skip to main content
Glama
JackXuyi

Current operating environment

getWifiInfo

Retrieve current device Wi-Fi connection details including network name, signal strength, and connection status to monitor network environment.

Instructions

获取当前设备的 Wi-Fi 信息

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler implementation for the 'getWifiInfo' tool. It fetches Wi-Fi networks using the 'systeminformation' library (si.wifiNetworks()) and returns the information as a JSON string in the tool response format.
    case "getWifiInfo": {
      const wifiInfo = await si.wifiNetworks();
      return {
        content: [{
          type: "text",
          text: JSON.stringify(wifiInfo, null, 2)
        }]
      };
    }
  • The schema/declaration of the 'getWifiInfo' tool in the list of available tools returned by the ListTools handler. Includes name, description, and input schema (empty object).
    {
      name: "getWifiInfo",
      description: "获取当前设备的 Wi-Fi 信息",
      inputSchema: {
        type: "object",
        properties: {},
        required: []
      }
    },
  • src/index.ts:787-791 (registration)
    Registration of the request handlers for listing tools (which includes getWifiInfo schema) and calling tools (which dispatches to the getWifiInfo handler).
    server.setRequestHandler(ListToolsRequestSchema, handleRequest);
    
    // 处理工具调用
    server.setRequestHandler(CallToolRequestSchema, handleCallToolRequest);
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states what the tool does but doesn't describe how it behaves: whether it returns connection status, SSID, signal strength, security type, or other Wi-Fi details. There's no mention of permissions needed, error conditions, or what format the information comes in.

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?

The description is a single, efficient sentence in Chinese that directly states the tool's purpose without any unnecessary words. It's perfectly front-loaded with the core functionality and wastes no space on redundant information.

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

Completeness2/5

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

Given this is a system information retrieval tool with no annotations and no output schema, the description is insufficient. It doesn't explain what specific Wi-Fi information will be returned (connection status, SSID, signal strength, etc.), which is critical context for an agent to understand what this tool provides versus similar tools.

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 has zero parameters with 100% schema description coverage, so the baseline is 4. The description appropriately doesn't discuss parameters since none exist, and the schema already fully documents the empty parameter set.

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 clearly states the tool's purpose as '获取当前设备的 Wi-Fi 信息' (Get current device's Wi-Fi information), which is a specific verb+resource combination. It distinguishes itself from siblings like getNetworkInfo or getAvailableNetworks by focusing specifically on Wi-Fi information rather than general network data or available networks.

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?

The description provides no guidance on when to use this tool versus alternatives. While it's clear this tool retrieves Wi-Fi information, there's no mention of when to choose it over similar tools like getNetworkInfo or getAvailableNetworks, nor any prerequisites or context for its use.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/JackXuyi/env-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server