action1-mcp-server

Switch a current monitor

action1_update_remote_session

Destructive

Update a remote session's current monitor setting. Provide the endpoint and session IDs to change the active display for the specified connection.

Instructions

Switch a current monitor. Changes the 'current_monitor' parameter for a specific remote session. Perm: remote_connect.

Input Schema

Name	Required	Description
`body`	No	Request body
`org_id`	No	Org UUID.
`confirm`	No	Required to execute. Exact string "YES".
`dry_run`	No	Default true (preview). Set false to execute.
`session_id`	Yes	Provide a specific remote session ID.
`endpoint_id`	Yes	Provide an endpoint ID.

Output Schema

Name	Required	Description	Default
`id`	No
`self`	No
`tool`	No
`type`	No
`dry_run`	No
`user_id`	No
`connected`	No
`current_ip`	No
`would_send`	No
`endpoint_name`	No
`enterprise_id`	No
`monitor_count`	No
`customer_email`	No
`remote_session`	No
`connection_type`	No
`current_monitor`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed21 schema fields changedv0.6.0Oct 26, 2026
- changedInput schema / $schema
```
Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
```
- changedInput schema / properties / body / description
```
Previous value: -"Request body (schema: object)"New value: +"Request body"
```
- addedInput schema / properties / body / properties
```
Added value: +{
+  "current_monitor": {
+    "description": "Switch to monitor 2.",
+    "type": "string"
+  }
+}
```
- changedOutput schema / $schema
```
Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
```
- changedOutput schema / additionalProperties
```
Previous value: -trueNew value: +{}
```
- addedOutput schema / properties / connected
```
Added value: +{}
```
- addedOutput schema / properties / connection_type
```
Added value: +{}
```
- addedOutput schema / properties / current_ip
```
Added value: +{}
```
- addedOutput schema / properties / current_monitor
```
Added value: +{}
```
- addedOutput schema / properties / customer_email
```
Added value: +{}
```
- addedOutput schema / properties / dry_run
```
Added value: +{}
```
- addedOutput schema / properties / endpoint_name
```
Added value: +{}
```
- addedOutput schema / properties / enterprise_id
```
Added value: +{}
```
- addedOutput schema / properties / id
```
Added value: +{}
```
- addedOutput schema / properties / monitor_count
```
Added value: +{}
```
- addedOutput schema / properties / remote_session
```
Added value: +{}
```
- addedOutput schema / properties / self
```
Added value: +{}
```
- addedOutput schema / properties / tool
```
Added value: +{}
```
- addedOutput schema / properties / type
```
Added value: +{}
```
- addedOutput schema / properties / user_id
```
Added value: +{}
```
- addedOutput schema / properties / would_send
```
Added value: +{}
```
First observedv0.5.0Jun 27, 2026

TDQS

B3.2/5.0

Behavior3/5

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

The 'Perm: remote_connect' note adds a genuine auth requirement not in the schema or annotations. However, with destructiveHint=true and a mandatory confirm="YES" / dry_run=false pattern in the schema, the description omits any warning that this is a state-changing, non-idempotent action requiring explicit confirmation.

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?

Three short sentences with the action front-loaded and no filler. Efficient, though the second sentence largely repeats the title.

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?

An output schema exists so return values need no explanation, but for a destructive, non-idempotent mutation the description should surface the dry_run/confirm safety protocol and scope (one session at a time). It is callable but under-specified behaviorally.

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%, so all six parameters are already documented in the schema. The description only restates the current_monitor target and implies a session ID, adding essentially nothing beyond the schema baseline.

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 and resource ('Switch a current monitor') and clarifies it mutates the 'current_monitor' field of a specific remote session. It is distinguishable from get_remote_session and create_endpoint_remote_session, though it never names those siblings.

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

Usage Guidelines2/5

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

There is no guidance on when to use this versus get_remote_session or create_endpoint_remote_session, and no mention of the required preview/confirm workflow. The agent must infer usage entirely from the schema.

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

Deploy Server