action1-mcp-server

Change an endpoint comment or name

action1_update_endpoint

Destructive

Update an endpoint's name, comment, or custom attributes to keep managed endpoint records accurate.

Instructions

Change an endpoint comment or name. Changes the user-defined 'comment', 'name' and custom attributes for the specified endpoint. Perm: manage_endpoint_attributes.

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
`OS`	No
`id`	No
`MAC`	No
`NIC`	No
`RAM`	No
`WiFi`	No
`disk`	No
`name`	No
`self`	No
`tool`	No
`type`	No
`user`	No
`video`	No
`custom`	No
`serial`	No
`status`	No
`address`	No
`comment`	No
`dry_run`	No
`CPU_name`	No
`CPU_size`	No
`platform`	No
`CPU_model`	No
`last_seen`	No
`would_send`	No
`device_name`	No
`architecture`	No
`manufacturer`	No
`agent_version`	No
`online_status`	No
`update_status`	No
`last_boot_time`	No
`missing_updates`	No
`organization_id`	No
`reboot_required`	No
`vulnerabilities`	No
`AD_security_groups`	No
`agent_install_date`	No
`subscription_status`	No
`AD_organization_unit`	No
`vulnerability_status`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed46 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: +{
+  "comment": {
+    "description": "New value for comment.",
+    "type": "string"
+  },
+  "custom:{Custom Attribute Name}": {
+    "description": "New value for custom attribute.",
+    "type": "string"
+  },
+  "name": {
+    "description": "New value for name.",
+    "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 / AD_organization_unit
```
Added value: +{}
```
- addedOutput schema / properties / AD_security_groups
```
Added value: +{}
```
- addedOutput schema / properties / CPU_model
```
Added value: +{}
```
- addedOutput schema / properties / CPU_name
```
Added value: +{}
```
- addedOutput schema / properties / CPU_size
```
Added value: +{}
```
- addedOutput schema / properties / MAC
```
Added value: +{}
```
- addedOutput schema / properties / NIC
```
Added value: +{}
```
- addedOutput schema / properties / OS
```
Added value: +{}
```
- addedOutput schema / properties / RAM
```
Added value: +{}
```
- addedOutput schema / properties / WiFi
```
Added value: +{}
```
- addedOutput schema / properties / address
```
Added value: +{}
```
- addedOutput schema / properties / agent_install_date
```
Added value: +{}
```
- addedOutput schema / properties / agent_version
```
Added value: +{}
```
- addedOutput schema / properties / architecture
```
Added value: +{}
```
- addedOutput schema / properties / comment
```
Added value: +{}
```
- addedOutput schema / properties / custom
```
Added value: +{}
```
- addedOutput schema / properties / device_name
```
Added value: +{}
```
- addedOutput schema / properties / disk
```
Added value: +{}
```
- addedOutput schema / properties / dry_run
```
Added value: +{}
```
- addedOutput schema / properties / id
```
Added value: +{}
```
- addedOutput schema / properties / last_boot_time
```
Added value: +{}
```
- addedOutput schema / properties / last_seen
```
Added value: +{}
```
- addedOutput schema / properties / manufacturer
```
Added value: +{}
```
- addedOutput schema / properties / missing_updates
```
Added value: +{}
```
- addedOutput schema / properties / name
```
Added value: +{}
```
- addedOutput schema / properties / online_status
```
Added value: +{}
```
- addedOutput schema / properties / organization_id
```
Added value: +{}
```
- addedOutput schema / properties / platform
```
Added value: +{}
```
- addedOutput schema / properties / reboot_required
```
Added value: +{}
```
- addedOutput schema / properties / self
```
Added value: +{}
```
- addedOutput schema / properties / serial
```
Added value: +{}
```
- addedOutput schema / properties / status
```
Added value: +{}
```
- addedOutput schema / properties / subscription_status
```
Added value: +{}
```
- addedOutput schema / properties / tool
```
Added value: +{}
```
- addedOutput schema / properties / type
```
Added value: +{}
```
- addedOutput schema / properties / update_status
```
Added value: +{}
```
- addedOutput schema / properties / user
```
Added value: +{}
```
- addedOutput schema / properties / video
```
Added value: +{}
```
- addedOutput schema / properties / vulnerabilities
```
Added value: +{}
```
- addedOutput schema / properties / vulnerability_status
```
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?

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the risk profile is covered; the description adds the concrete authorization requirement ('Perm: manage_endpoint_attributes'), which is genuine value beyond structured data. However it never mentions the preview/execute workflow (dry_run defaults true, confirm="YES" required) at the description level, leaving the most consequential behavioral detail to the schema.

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?

Two short sentences with the mutation target front-loaded, no filler. The second sentence partially restates the first ("Change ... comment or name" then "Changes the user-defined 'comment', 'name'..."), so a small amount of redundancy remains.

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, and the permission requirement is stated. But for a destructive, non-idempotent mutation behind a two-step dry_run/confirm gate, the description says nothing about the safety workflow or which fields are omitted vs. cleared, leaving context that would materially help an agent call it correctly.

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 the schema already documents all five parameters, establishing baseline 3. The description names the fields the body can carry but adds no format, key-naming, or custom-attribute syntax detail beyond what the schema's 'custom:{Custom Attribute Name}' pattern shows.

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 ("Change an endpoint comment or name") and enumerates the mutable fields (comment, name, custom attributes), which separates it from sibling mutations like action1_move_endpoint or action1_update_group. It does not explicitly name a sibling alternative, so it stops short of 5.

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 when-to-use or when-not guidance and no mention of alternatives among the many endpoint-mutating siblings. The only routing signal is the permission name 'manage_endpoint_attributes', which implies the caller needs that scope but doesn't tell an agent when to pick this tool over others.

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

Deploy Server