Skip to main content
Glama

net-web-media

mac_oui_inspect

Parse MAC-48 / EUI-48 addresses, identify U/L local vs universal bit and unicast/multicast bit, format notations (colon/dash/Cisco), and compute EUI-64 link-local IPv6.

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": "mac_oui_inspect"
  }
}

Input Schema

NameRequiredDescriptionDefault
macNo00:1A:2B:3C:4D:5E
textNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden. It implies a pure, side-effect-free computation by describing only parsing/derivation, but it never states that it is read-only, that it makes no network or vendor lookup, or how malformed input is handled. It usefully discloses the set of computations performed, which is more than the schema reveals, but the safety/error profile is left implicit.

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 dense sentence that front-loads the primary action and then lists the outputs in a scannable order. No filler or repetition, though the enumeration is packed enough that it reads as a feature list rather than a guided explanation.

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

Completeness3/5

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

The tool is a simple two-parameter computation with no output schema, so the description should say something about the result shape and about the second parameter. It covers the computational scope well but leaves the return structure, the 'text' parameter, and invalid-input behavior undocumented.

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 0% for both parameters, and the description does not name 'mac' or 'text' or explain their roles, so an agent cannot tell from the text what 'text' is for. However, the single-address parse context and the default MAC value make the primary parameter's purpose reasonably inferable from the schema itself, so this is a baseline rather than a failing grade.

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 names a concrete verb ('Parse') and resources ('MAC-48 / EUI-48 addresses') and enumerates the four things the tool returns: U/L bit, unicast/multicast bit, notation formatting, and EUI-64 link-local derivation. It is clearly distinguishable from siblings like ipv4_representation_convert or ipv6_cidr_calculate, which operate on different address families. It stops short of a 5 because the tool name advertises OUI inspection while the description never mentions vendor/OUI identification, leaving ambiguity about whether that capability exists.

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 or when-not-to-use guidance, no mention of alternatives, and no statement of preconditions (e.g., that input must be a valid 48-bit address). An agent must infer the use case entirely from the verb list.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources