Skip to main content
Glama
vandreus

UniFi MCP Server

by vandreus

unblock_client

Unblock a client from the UniFi network to restore internet access after being blocked by network policies or security measures.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The primary handler for the 'unblock_client' MCP tool. It invokes the UniFi API via unifi.unblockClient, handles the response, and returns formatted text output.
    handler: async ({ hostId, siteId, mac }) => {
      const result = await unifi.unblockClient(hostId, siteId, mac);
      return {
        content: [{ type: 'text', text: `Client ${mac} has been unblocked. ${JSON.stringify(result, null, 2)}` }]
      };
    }
  • Zod schema defining input parameters for the unblock_client tool: hostId, siteId, and mac address.
    schema: z.object({
      hostId: z.string().describe('The host ID'),
      siteId: z.string().describe('The site ID'),
      mac: z.string().describe('The client MAC address')
    }),
  • src/server.js:30-30 (registration)
    Registration of the clientTools module (containing unblock_client) to the MCP server via registerToolsFromModule, which calls server.tool() for each tool.
    registerToolsFromModule(clientTools);
  • Underlying helper function that makes the actual POST request to the UniFi Cloud API to unblock the client.
    export async function unblockClient(hostId, siteId, mac) {
      const response = await cloudApi.post(`/v1/hosts/${hostId}/sites/${siteId}/clients/${mac}/unblock`);
      return response.data;
    }
  • src/server.js:4-4 (registration)
    Import of the clientTools module, which includes the unblock_client tool definition.
    import { clientTools } from './tools/clients.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