Skip to main content
Glama
vandreus

UniFi MCP Server

by vandreus

get_clients_for_site

Retrieve connected client devices from a UniFi network site to monitor network usage and manage access.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The MCP tool handler for 'get_clients_for_site' that invokes the UniFi API helper and returns formatted JSON response.
    handler: async ({ hostId, siteId }) => {
      const clients = await unifi.getClientsForSite(hostId, siteId);
      return {
        content: [{ type: 'text', text: JSON.stringify(clients, null, 2) }]
      };
    }
  • Zod input schema validating hostId and siteId parameters.
    schema: z.object({
      hostId: z.string().describe('The host ID'),
      siteId: z.string().describe('The site ID')
    }),
  • src/server.js:30-30 (registration)
    Registers the clientTools object (containing get_clients_for_site) with the MCP server via registerToolsFromModule.
    registerToolsFromModule(clientTools);
  • Helper function in unifi-client that performs the actual UniFi Cloud API GET request for site clients.
    export async function getClientsForSite(hostId, siteId) {
      const response = await cloudApi.get(`/v1/hosts/${hostId}/sites/${siteId}/clients`);
      return response.data;
    }
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