Skip to main content
Glama
matt-coppinger

Horizon MCP Server

by matt-coppinger
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

disconnect_sessions

Destructive

Disconnect one or more user sessions while leaving their applications running; use logoff_sessions to fully terminate them.

Instructions

Disconnect one or more user sessions (sessions remain active, clients are disconnected).

The user's applications keep running. Use logoff_sessions to fully terminate sessions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmNoOnly used when the server runs with HORIZON_CONFIRMATION=flag (clients without elicitation). Otherwise the user is asked to confirm directly in the client.
session_idsYesList of session IDs to disconnect. The session remains active but the client is disconnected.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.0
    • addedInput schema / properties / confirm
      Added value: +{
+  "default": false,
+  "description": "Only used when the server runs with HORIZON_CONFIRMATION=flag (clients without elicitation). Otherwise the user is asked to confirm directly in the client.",
+  "type": "boolean"
+}
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds genuinely useful nuance beyond them: the session remains active and the user's applications keep running, which softens and disambiguates the 'destructive' hint. It does not discuss confirmation flow or permissions, but the confirm parameter schema covers the former.

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 tight sentences with zero waste; the core behavior (sessions stay active, clients disconnect) is front-loaded and the routing hint to logoff_sessions follows. Every sentence earns its place.

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

Completeness5/5

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

With an output schema present, return values need not be described, and annotations plus schema cover safety and parameters. The description supplies the one non-obvious behavioral fact (apps keep running, session survives) and the correct alternative, leaving nothing an agent needs missing.

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%, so both parameters (session_ids and confirm) are fully documented in the schema itself. The description adds no syntax, format, or batching detail beyond what the schema provides, so the baseline of 3 is appropriate.

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 states a specific verb (disconnect) and resource (user sessions) with clear scope (one or more), and explicitly distinguishes itself from the sibling logoff_sessions. An agent can tell it apart from logoff_sessions, reset_or_restart_sessions, and send_message_to_sessions without opening any schema.

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

Usage Guidelines5/5

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

It names the alternative explicitly ('Use logoff_sessions to fully terminate sessions') and gives the condition that selects it, so the choice between disconnect and logoff is unambiguous. The parenthetical also clarifies when this tool is the right fit (sessions must remain active).

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