Skip to main content
Glama
JackXuyi

Current operating environment

getNetworkInfo

Retrieve network configuration details from your current system to diagnose connectivity issues and monitor network status.

Instructions

获取当前系统的网络信息

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler implementation for the 'getNetworkInfo' tool. Retrieves network interfaces using Node.js 'os.networkInterfaces()' and returns the data as a JSON-formatted text response.
    case "getNetworkInfo": {
      const networkInfo = {
        networkInterfaces: os.networkInterfaces()
      };
    
      return {
        content: [{
          type: "text",
          text: JSON.stringify(networkInfo, null, 2)
        }]
      };
    }
  • src/index.ts:56-63 (registration)
    Registration of the 'getNetworkInfo' tool in the listTools handler response. Defines the tool name, description, and input schema (empty object).
      name: "getNetworkInfo",
      description: "获取当前系统的网络信息",
      inputSchema: {
        type: "object",
        properties: {},
        required: []
      }
    },
  • Input schema definition for the 'getNetworkInfo' tool, specifying an empty object with no required properties.
    inputSchema: {
      type: "object",
      properties: {},
      required: []
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states what the tool does ('获取当前系统的网络信息') but doesn't disclose behavioral traits like what specific network information is returned (e.g., interfaces, IP addresses, connectivity status), whether it requires permissions, or if it's read-only/safe. For a tool with zero annotation coverage, this is a significant gap in transparency.

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: '获取当前系统的网络信息'. It's front-loaded with the core action and resource, with zero wasted words. Every part of the sentence directly contributes to understanding the tool's purpose.

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 the complexity (retrieving system network information), lack of annotations, and no output schema, the description is incomplete. It doesn't specify what '网络信息' includes (e.g., interfaces, IPs, DNS), making it hard for an agent to understand the return value. For a tool with no structured output documentation, the description should provide more context about the expected data.

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 0 parameters, and schema description coverage is 100% (though empty). With no parameters to document, the description doesn't need to compensate for schema gaps. A baseline of 4 is appropriate since there are no parameters to explain beyond what the schema already indicates (none).

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 '获取当前系统的网络信息' (Get current system network information) clearly states the verb ('获取' - get) and resource ('网络信息' - network information). It distinguishes from siblings like getIpv4Info, getIpv6Info, getWifiInfo, and getAvailableNetworks by specifying it retrieves general network information rather than specific aspects. However, it doesn't explicitly contrast with these alternatives, keeping it from a perfect score.

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. With siblings like getIpv4Info, getIpv6Info, getWifiInfo, and getAvailableNetworks that retrieve specific network details, there's no indication whether this tool aggregates these or provides different information. It lacks explicit when/when-not instructions or named alternatives.

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