Skip to main content
Glama
vandreus

UniFi MCP Server

by vandreus

find_device_by_mac

Locate specific network devices using MAC addresses to identify and manage equipment within UniFi infrastructure.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function that normalizes the input MAC address, retrieves all devices using unifi.listAllDevices(), filters devices matching the MAC, and returns a JSON response with search details and matches.
    handler: async ({ mac }) => {
      const normalizedMac = mac.toLowerCase().replace(/[:-]/g, '');
      const allDevices = await unifi.listAllDevices();
      const devices = allDevices.data || [];
    
      const matches = devices.filter(d => {
        const deviceMac = (d.mac || '').toLowerCase().replace(/[:-]/g, '');
        return deviceMac === normalizedMac || deviceMac.includes(normalizedMac);
      });
    
      return {
        content: [{
          type: 'text',
          text: JSON.stringify({
            searchMac: mac,
            matchCount: matches.length,
            matches
          }, null, 2)
        }]
      };
    }
  • Zod schema defining the input parameter 'mac' as a string for the tool.
    schema: z.object({
      mac: z.string().describe('The MAC address to search for')
    }),
  • src/server.js:29-29 (registration)
    Registers the deviceTools module, including the find_device_by_mac tool, by calling registerToolsFromModule which invokes server.tool for each tool in the module.
    registerToolsFromModule(deviceTools);
  • src/server.js:3-3 (registration)
    Import of the deviceTools module containing the find_device_by_mac tool definition.
    import { deviceTools } from './tools/devices.js';
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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/vandreus/Unifi-MCP'

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