Skip to main content
Glama
vandreus

UniFi MCP Server

by vandreus

find_client_by_mac

Locate and retrieve client device information in a UniFi network by searching with its MAC address to identify connected devices.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The core handler function implementing the 'find_client_by_mac' tool. It normalizes the MAC address, fetches all clients via unifi.listAllClients(), filters for exact or partial MAC matches, and returns a structured JSON response with match details.
    handler: async ({ mac }) => {
      const normalizedMac = mac.toLowerCase().replace(/[:-]/g, '');
      const allClients = await unifi.listAllClients();
      const clients = allClients.data || [];
    
      const matches = clients.filter(c => {
        const clientMac = (c.mac || '').toLowerCase().replace(/[:-]/g, '');
        return clientMac === normalizedMac || clientMac.includes(normalizedMac);
      });
    
      return {
        content: [{
          type: 'text',
          text: JSON.stringify({
            searchMac: mac,
            matchCount: matches.length,
            matches
          }, null, 2)
        }]
      };
    }
  • Zod schema defining the input parameters for the tool: a required 'mac' string.
    schema: z.object({
      mac: z.string().describe('The MAC address to search for')
    }),
  • src/server.js:30-30 (registration)
    Line registering the clientTools module (which includes find_client_by_mac) with the MCP server via the registerToolsFromModule utility.
    registerToolsFromModule(clientTools);
  • Helper function called by the tool handler to retrieve all clients across hosts/sites. (Note: full implementation not read, but key dependency.)
    export async function listAllClients() {
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