Skip to main content
Glama
Sign In
UniFi MCP Server

UniFi MCP Server

by enuno
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

select_controller

Selects the UniFi controller for this session's later tool calls; per-call controller arguments override it.

Instructions

Choose the controller this session's later tool calls target.

A tool call's own controller argument still takes precedence.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "select_controller"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesA controller name from list_controllers

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.6.4
    • addedInput schema / properties / name / description
      Added value: +"A controller name from list_controllers"
  2. Addedv0.6.0

TDQS

A3.8/5.0
Behavior3/5

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

The annotations are empty, so the description must disclose behavior itself. It does disclose the important trait: setting a session-level default and how it interacts with per-call overrides. It does not say what happens if the name is invalid, whether an error is raised, or how long the setting persists.

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

Conciseness5/5

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

Two short sentences present the purpose first, then the precedence exception. There is no filler, and every sentence conveys information the agent needs.

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

Completeness4/5

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

An output schema exists, so the return value needs no explanation. For this stateful session tool, the description covers scope and override rules, but it omits failure modes and lifetime/persistence details.

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?

The schema describes the single parameter 100%, and its description already says the value must come from list_controllers. The tool description adds nothing beyond that, which is the expected baseline when the schema carries the semantics.

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

Purpose4/5

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

The description states a specific action and its scope: it chooses the controller that later tool calls in the same session will target. That clearly distinguishes it from sibling tools that read state, such as get_active_controller and list_controllers, but it never names those siblings explicitly.

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

Usage Guidelines4/5

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

It explains when the setting matters, namely that it affects later calls in the same session, and it adds a precedence rule: a per-call `controller` argument overrides it. It does not explicitly tell the agent to call list_controllers first; that guidance appears only in the parameter schema.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools