Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

system-networkInterface

Returns a random network interface with a chosen type and schema for generating fake system network data in tests and demos.

Instructions

Returns a random network interface.

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": "system-networkInterface"
  }
}

Input Schema

NameRequiredDescriptionDefault
interfaceTypeNoThe interface type. Can be one of 'en', 'wl', 'ww'.
interfaceSchemaNoThe interface schema. Can be one of 'index', 'slot', 'mac', 'pci'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and falls well short: it does not say whether the two parameters constrain the random draw or are ignored, nor whether the same call can yield different results. The return shape (a string? an object with index/slot/mac?) is never hinted at and no output schema exists to compensate.

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 zero wasted words. Brevity is appropriate, though the spareness borders on under-specification rather than tight editing.

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?

For a tool with two optional filtering-style parameters, no annotations, and no output schema, the description should at minimum explain how the parameters interact with the random selection and what is returned. Neither is provided, leaving meaningful ambiguity about call behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and both parameters are enums with documented values, so the schema does the heavy lifting. The description adds nothing beyond that baseline and its 'random' framing could even suggest the parameters are irrelevant to selection.

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?

States a specific verb and resource ('Returns a random network interface'), which is unambiguous on its own. It does not distinguish itself from the many sibling generators, but within the faker-style family the purpose is immediately graspable.

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 when-to-use guidance, no mention of when the optional filters should be supplied, and no reference to any alternative tool. The agent must infer usage entirely from the schema.

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