Skip to main content
Glama
JackXuyi

Current operating environment

getIpv6Info

Retrieve IPv6 address details for the current device to identify network configuration and connectivity status.

Instructions

获取当前设备的 IPv6 信息

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler implementation for the 'getIpv6Info' tool. It retrieves all network interfaces using os.networkInterfaces(), filters for IPv6 addresses, structures the data by interface, and returns it as JSON text.
    case "getIpv6Info": {
      const networkInterfaces = os.networkInterfaces();
      const ipInfo: Record<string, { address: string; netmask: string; family: string; internal: boolean }[]> = {};
    
      for (const [interfaceName, interfaces = []] of Object.entries(networkInterfaces)) {
        const ipv6Interfaces = interfaces
          .filter((info) => info.family === 'IPv6')
          .map((info) => ({
            address: info.address,
            netmask: info.netmask,
            family: info.family,
            internal: info.internal
          }));
        if (ipv6Interfaces.length > 0) {
          ipInfo[interfaceName] = ipv6Interfaces;
        }
      }
    
      return {
        content: [{
          type: "text",
          text: JSON.stringify(ipInfo, null, 2)
        }]
      };
  • Schema definition for the 'getIpv6Info' tool, including name, description, and input schema (empty object as no parameters required). This is part of the tools list returned by ListToolsRequest.
    {
      name: "getIpv6Info",
      description: "获取当前设备的 IPv6 信息",
      inputSchema: {
        type: "object",
        properties: {},
        required: []
      }
    },
  • src/index.ts:790-790 (registration)
    Registration of the CallToolRequest handler function, which contains the switch case dispatching to the getIpv6Info implementation.
    server.setRequestHandler(CallToolRequestSchema, handleCallToolRequest);
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool retrieves IPv6 information but doesn't specify what that includes (e.g., addresses, configuration, status), whether it requires permissions, if it's read-only or has side effects, or how it handles errors. 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: '获取当前设备的 IPv6 信息'. It's front-loaded with the core action and resource, with zero wasted words. Every part of the sentence contributes directly to understanding the tool's function, making it highly concise and well-structured.

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 lack of annotations and output schema, the description is incomplete. It doesn't explain what IPv6 information is returned (e.g., addresses, subnet, gateway), the format of the output, or any behavioral aspects like error handling. For a tool that likely returns structured data, more context is needed to guide the agent effectively.

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%, meaning there are no parameters to document. The description doesn't need to add parameter semantics, so it meets the baseline for this scenario. It appropriately focuses on the tool's purpose without unnecessary parameter details.

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: '获取当前设备的 IPv6 信息' (Get the current device's IPv6 information). It specifies the verb (获取/get) and resource (IPv6 信息/IPv6 information) with the scope of '当前设备' (current device). However, it doesn't explicitly differentiate from its sibling 'getIpv4Info' or other network-related tools like 'getNetworkInfo' or 'getProxyInfo', which prevents 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. It doesn't mention sibling tools like 'getIpv4Info' for IPv4 data, 'getNetworkInfo' for broader network details, or 'getProxyInfo' for proxy settings. There's no context on prerequisites, exclusions, or specific use cases, leaving the agent to infer usage from the name alone.

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