Skip to main content
Glama

list-devices

List all network devices including switches, access points, gateways, and cameras. Filter by host or device type, and project specific fields to reduce response size.

Instructions

List all devices across hosts (switches, APs, gateways, cameras)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hostIdNoFilter by host ID
typeNoFilter by device type (e.g., 'uap', 'usw', 'ugw')
extractFieldsNoComma-separated dotted paths to project from response (e.g. 'id,name,owner.name,columns.*.name'). Use `*` as wildcard for arrays/objects. Wrap field names with dots in backticks. Reduces response tokens dramatically on large entities.

Implementation Reference

  • The main handler function for list-devices. It builds query params from hostId/type filters, calls GET /devices on the UniFi client, and optionally extracts fields or returns the full response data.
    export async function listDevices(params: z.infer<typeof listDevicesSchema>) {
      const queryParams: Record<string, string | undefined> = {};
      if (params.hostId) queryParams.hostId = params.hostId;
      if (params.type) queryParams.type = params.type;
    
      const response = await unifiClient.get<{ data: unknown[] }>("/devices", queryParams);
      if (params.extractFields) return response.data;
      return applyExtractFields(
        response.data,
        "*.hostId,*.hostName,*.devices.*.id,*.devices.*.name,*.devices.*.model,*.devices.*.status,*.devices.*.version",
      );
    }
  • Zod schema for list-devices input validation. Accepts optional hostId (filter by host), type (filter by device type e.g. 'uap', 'usw', 'ugw'), and extractFields.
    export const listDevicesSchema = z.object({
      hostId: z.string().optional().describe("Filter by host ID"),
      type: z.string().optional().describe("Filter by device type (e.g., 'uap', 'usw', 'ugw')"),
      extractFields: ef,
    });
  • src/index.ts:121-123 (registration)
    Registration of the 'list-devices' tool with its description, schema, and handler wrapped via wrapToolHandler.
    tool("list-devices",
      "List all devices across hosts (switches, APs, gateways, cameras)",
      listDevicesSchema.shape, wrapToolHandler(listDevices));
  • src/index.ts:23-23 (registration)
    Import of listDevicesSchema and listDevices from './tools/devices.js' into the main entry point.
    import { listDevicesSchema, listDevices } from "./tools/devices.js";
Behavior2/5

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

No annotations are provided, so the description carries the burden of behavioral disclosure. However, it only states 'list all devices' without mentioning pagination, rate limits, authentication, or other operational behaviors.

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

Conciseness4/5

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

The description is a single, efficient sentence that conveys the core purpose. It is front-loaded with the action and resource, but could be slightly enhanced with additional context without becoming verbose.

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

Completeness3/5

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

Given the absence of an output schema and annotations, the description is minimal. It lists device types in parentheses, which adds some context, but lacks details on pagination, result structure, or handling of large datasets.

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

Parameters3/5

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

Schema description coverage is 100%, with all three parameters described in the input schema. The description adds no additional meaning beyond the schema, so baseline score of 3 applies.

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

Purpose5/5

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

The description clearly states the action 'list' and resource 'devices', with scope 'across hosts' and examples of device types (switches, APs, gateways, cameras). This is specific and distinguishes from sibling tools like list-hosts or list-sites.

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

Usage Guidelines3/5

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

No explicit when-to-use or when-not-to-use guidance is provided. The description implies usage context through the mention of device types, but it does not mention alternatives or prerequisites.

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/us-all/unifi-mcp-server'

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