Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

osint_mac_vendor_lookup

Read-onlyIdempotent

Identify the manufacturer of any network device by its MAC address using a local OUI lookup. Works offline with no external requests.

Instructions

MAC Address Vendor Lookup. Identify the hardware manufacturer of a network device from its MAC address by matching the 24-bit OUI prefix against a built-in IEEE OUI table. Runs locally: no outbound request to macvendors.com or any external registry, so it is read-only, non-destructive, deterministic, and works offline. Use this to attribute an existing MAC to a vendor; use networking_mac_address_generator to create random/vendor MACs, and osint_vin_decoder to decode a vehicle VIN instead of a network address. Rate limited to 60 requests/minute for anonymous callers. Returns the normalized address, the OUI, the matched vendor (null when the OUI is not in the bundled subset), vendor details, and a structural analysis (unicast/multicast, locally vs universally administered, likely-virtual flag).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mac_addressYesMAC address to look up. Accepts 12 hex digits with any or no separator (colon, hyphen, dot); case-insensitive. Must contain exactly 12 hex characters (6 bytes) after separators are stripped.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNoTrue when the lookup completed; false on invalid input.
errorNoPresent only when success is false; human-readable reason (blank or malformed MAC).
resultNoLookup result; present when success is true.
Behavior5/5

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

Beyond annotations (readOnlyHint, destructiveHint, idempotentHint), the description adds that it runs locally, makes no outbound requests, is deterministic, works offline, and is rate-limited. This provides complete behavioral transparency.

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?

Description is moderately long but well-organized. Core purpose is front-loaded, and every sentence adds value. Could be slightly more concise, but still effective. Score 4.

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

Completeness5/5

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

Tool has output schema (not shown but noted) and description explains return fields (normalized address, OUI, vendor, details, structural analysis). Input is simple. Description is complete for effective use.

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?

Schema already has 100% coverage with detailed description for mac_address. The description adds context about OUI prefix matching and the built-in table, but the schema covers input format well. Slight added value justifies a 4.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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: 'MAC Address Vendor Lookup' and explains it identifies the hardware manufacturer from a MAC address using a built-in OUI table. It distinguishes itself from sibling tools like networking_mac_address_generator and osint_vin_decoder.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use ('attribute an existing MAC to a vendor') and when not to use (alternatives for creating MACs or decoding VINs). Also mentions rate limiting (60 req/min) for proper usage context.

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/Jambozx/onlinecybertools-mcp-server'

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