action1-mcp-server

Start a new remote session

action1_create_endpoint_remote_session

Destructive

Start a new remote assistance session on a specified endpoint by sending a connection request, with preview and confirmation controls for safe execution.

Instructions

Start a new remote session. Sends a request to the endpoint to start a new remote session. Perm: remote_connect.

Input Schema

Name	Required	Description
`body`	Yes	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.
`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.

Changed22 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: +{
+  "connection_type": {
+    "const": "assistance",
+    "type": "string"
+  },
+  "current_ip": {
+    "type": "string"
+  }
+}
```
- addedInput schema / properties / body / required
```
Added value: +[
+  "connection_type"
+]
```
- 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.1/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, idempotentHint=false, so the safety profile is covered. The description adds the required permission (remote_connect), which is genuine context beyond annotations, but says nothing about reversibility, the confirm gate, or what the session creates.

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

Conciseness3/5

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

It is short and front-loaded, but the second sentence is pure redundancy ("Sends a request to the endpoint to start a new remote session") and the permission note is tacked on rather than structured.

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?

Output schema exists and schema coverage is complete, so return values and parameter details are covered elsewhere. Still, for a destructive, open-world creation call, the description omits the confirm="YES" execution gate and the dry_run default-to-preview behavior that most affect correct invocation.

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 every parameter (endpoint_id, org_id, body.connection_type, confirm, dry_run) is already documented in the schema. The description mentions no parameters at all, so baseline 3 is appropriate.

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 first sentence states a specific verb and resource (start a remote session) that an agent can act on. However, it never differentiates from its close siblings get_remote_session and update_remote_session, and the second sentence merely restates the first with extra words.

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?

The only guidance is "Perm: remote_connect," which is a permission prerequisite rather than when-to-use guidance. Nothing indicates when to open a session versus inspecting one with get_remote_session, nor any warning about the destructive/open-world nature of the call.

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

Deploy Server