Skip to main content
Glama

getNetworkInterfaces

Retrieve network interface details to identify IP addresses, MAC addresses, and connection status for system diagnostics and monitoring.

Instructions

Get network interface information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function executes os.networkInterfaces() and returns the interfaces as prettified JSON in the required MCP content format.
    handler: async () => {
      const interfaces = os.networkInterfaces();
      return {
        content: [{
          type: 'text',
          text: JSON.stringify(interfaces, null, 2)
        }]
      };
    }
  • Input schema defining no required parameters for the getNetworkInterfaces tool.
    inputSchema: {
      type: 'object',
      properties: {}
    },
  • Tool definition and registration within the networkTools export object.
    getNetworkInterfaces: {
      name: 'getNetworkInterfaces',
      description: 'Get network interface information',
      inputSchema: {
        type: 'object',
        properties: {}
      },
      handler: async () => {
        const interfaces = os.networkInterfaces();
        return {
          content: [{
            type: 'text',
            text: JSON.stringify(interfaces, null, 2)
          }]
        };
      }
    },
  • src/index.ts:28-35 (registration)
    Registration of networkTools (including getNetworkInterfaces) into the central allTools object used by MCP server handlers for listing and calling tools.
    const allTools: ToolKit = {
      ...systemTools,
      ...networkTools,
      ...geoTools,
      ...generatorTools,
      ...dateTimeTools,
      ...securityTools
    };
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. 'Get network interface information' implies a read-only operation, but it doesn't specify what information is returned (e.g., IP addresses, status, metrics), whether it requires permissions, or if there are rate limits. This leaves significant gaps for a tool with zero annotation coverage.

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 with zero waste. It's front-loaded with the core purpose, making it easy to parse quickly. Every word earns its place without redundancy or unnecessary elaboration.

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 'network interface information' entails (e.g., list of interfaces, detailed stats), leaving the agent uncertain about the tool's behavior and output. For a tool with no structured support, this minimal description is inadequate.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate here. A baseline of 4 is given because the schema fully handles the parameter semantics, and the description doesn't need to compensate.

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 network interface information' clearly states the verb ('Get') and resource ('network interface information'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'getSystemInfo' or 'getPublicIP' that might overlap in networking context, preventing 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 'getSystemInfo' (which might include network data), 'getPublicIP', 'pingHost', and 'traceroute', there's no indication of this tool's specific scope or prerequisites, leaving the agent to guess based on 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/cyanheads/toolkit-mcp-server'

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