Skip to main content
Glama
Sign In
mgcrea

@mgcrea/mcp-unifi-protect

by mgcrea
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

UniFi Protect: Auth Logout

unifi_protect_auth_logout
DestructiveIdempotent

Clear the cached UniFi Protect session and delete its session file so the next call logs in again with the configured credentials. Use it after changing accounts or to remove the cookie from disk.

Instructions

Drop the cached session and delete the session file. The next call logs in again from the configured username and password, so this does not lock anything out — use it to clear a session after changing accounts, or to remove the cookie from disk.

Input Schema

NameRequiredDescriptionDefault
confirmYesMust be true. Explicit acknowledgement that this changes the console's state.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observedv0.3.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, but the description adds important nuance: the destructive action is limited to cached session state and auto-recovers on the next call, which substantially reduces the perceived risk. It does not mention concurrency or disk side effects beyond the cookie, keeping it just short of 5.

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 sentences, front-loaded with the mutation, followed by recovery behavior and use cases. Every sentence earns its place.

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?

A destructive mutation with one required confirm flag and no output schema; the description explains the effect and the recovery path, which is the critical context. Minor gap: no mention of what is returned or failure modes, but unnecessary given the simplicity.

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 coverage is 100% and the single confirm parameter is fully documented in the schema. The description adds no parameter details, so the baseline 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?

States a specific action on a specific resource: drop the cached session and delete the session file. This distinguishes it from auth_login and auth_status among the siblings without ambiguity.

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?

Gives concrete use cases (after changing accounts, or removing the cookie from disk) and clarifies it won't lock the user out since the next call re-authenticates. It doesn't explicitly compare to auth_login or auth_status, but the usage context is clear enough for correct selection.

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