Horizon MCP Server

end_remote_application

Destructive

Terminate a specific remote application in a session, force-closing it and losing unsaved data. Confirm with the user before calling to avoid data loss.

Instructions

Terminate a specific remote application running in a session.

CAUTION: The application will be force-closed. Unsaved data will be lost. Confirm with the user before calling this.

Input Schema

TableJSON Schema

Name	Required	Description
`confirm`	No	Only used when the server runs with HORIZON_CONFIRMATION=flag (clients without elicitation). Otherwise the user is asked to confirm directly in the client.
`session_id`	Yes	Session ID
`remote_application_id`	Yes	Remote application ID to terminate. Use diagnose_session with aspects=['remote_applications'] to find IDs.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.2.0Sep 30, 2026

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"
+}

First observedv0.1.0Sep 10, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, so the description earns credit for going beyond the flag: it states the application is force-closed and that unsaved data will be lost, which tells the agent the concrete consequence rather than a generic 'destructive' label. It also flags the user-confirmation obligation, which is real workflow context not captured by annotations.

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?

Three short sentences: purpose first, then the CAUTION, then the required action. Every sentence carries distinct information and nothing is padded.

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?

With an output schema present and full parameter documentation in the schema, the description only needs to carry purpose and risk, which it does. The one remaining gap is that it never situates the tool relative to the session-termination siblings, which matters for a mutation with irreversible effects.

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%, including the confirm parameter's HORIZON_CONFIRMATION behavior and a pointer to diagnose_session for finding remote_application_id. The description adds no parameter meaning beyond what the schema already documents, so the baseline 3 applies.

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?

States a specific verb (terminate) and resource (a remote application running in a session), with the scope narrowed to a single identified application. It is reasonably distinguishable from the session-level siblings like logoff_sessions and disconnect_sessions, though it never explicitly contrasts itself with them.

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?

The description gives a clear precondition for calling — confirm with the user first — but offers no guidance on when to use this versus logoff_sessions, disconnect_sessions, or reset_or_restart_sessions, which are the nearest alternatives for ending session activity. Usage is implied rather than routed.

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

Deploy Server