Skip to main content
Glama
vandreus

UniFi MCP Server

by vandreus

get_doors_status_summary

Retrieve a summary of all door access statuses across a UniFi network to monitor entry points and security states.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that implements the core logic of get_doors_status_summary: fetches all doors, computes counts for locked/unlocked/online/offline, builds a summary with door details, and returns it as JSON text.
    handler: async ({ hostId }) => {
      const doorsResponse = await unifi.listDoors(hostId);
      const doors = doorsResponse.data || [];
    
      const summary = {
        total: doors.length,
        locked: 0,
        unlocked: 0,
        online: 0,
        offline: 0,
        doors: []
      };
    
      doors.forEach(door => {
        // Count lock status
        if (door.lockState === 'LOCKED' || door.isLocked) {
          summary.locked++;
        } else {
          summary.unlocked++;
        }
    
        // Count connection status
        if (door.state === 'CONNECTED' || door.isConnected) {
          summary.online++;
        } else {
          summary.offline++;
        }
    
        // Add door info
        summary.doors.push({
          id: door.id,
          name: door.name,
          lockState: door.lockState,
          state: door.state
        });
      });
    
      return {
        content: [{ type: 'text', text: JSON.stringify(summary, null, 2) }]
      };
    }
  • Zod schema defining the input parameters for the tool: requires hostId string.
    schema: z.object({
      hostId: z.string().describe('The host ID')
    }),
  • src/server.js:32-32 (registration)
    Registers the accessTools module, which includes get_doors_status_summary, by calling registerToolsFromModule(accessTools). This iterates over the tools object and calls server.tool(name, schema, handler) for each.
    registerToolsFromModule(accessTools);
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