action1-mcp-server

List endpoints from the group

action1_list_group_contents

Read-onlyIdempotent

List endpoints in a specified group to audit membership or target devices, with filters for OS, status, update, vulnerability, and reboot state. Supports pagination and markdown or JSON output.

Instructions

List endpoints from the group. Lists all endpoints included in the specified group. Perm: view_endpoints.

Input Schema

Name	Required	Description
`os`	No	Filter by operation system.
`from`	No	Provide the number of the first record to be returned.
`limit`	No	Set the maximum number of items to be returned (the page size).
`cursor`	No	next_cursor of the previous call; takes precedence over from.
`fields`	No	Some API requests support the optional 'fields' parameter that specifies which object...
`filter`	No	Provide a case-insensitive substring to filter and narrow down returned results (i.e., if...
`org_id`	No	Org UUID.
`sortby`	No	Define the sorting order by a certain field.
`status`	No	Filter by online status.
`verbose`	No	Skip per-item compactor.
`group_id`	Yes	Provide an endpoint group ID.
`auto_paginate`	No	Walk pages until limit or the size budget; then continue with next_cursor.
`online_status`	No	Filter by last seen online status.
`update_status`	No	Filter by update status.
`reboot_required`	No	Filter by reboot requirement of the endpoint.
`response_format`	No	Output format. Default markdown.
`vulnerability_status`	No	Filter by vulnerability status.

Output Schema

Name	Required	Description	Default
`note`	No
`count`	Yes
`items`	Yes
`total`	No
`has_more`	No
`next_cursor`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed16 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 / auto_paginate / description

Previous value: -"Walk all pages."New value: +"Walk pages until limit or the size budget; then continue with next_cursor."

changedInput schema / properties / cursor / description

Previous value: -"Pagination cursor."New value: +"next_cursor of the previous call; takes precedence over from."

addedInput schema / properties / from / maximum
```
Added value: +9007199254740991
```
addedInput schema / properties / from / minimum
```
Added value: +0
```
addedInput schema / properties / limit / maximum
```
Added value: +50000
```
addedInput schema / properties / limit / minimum
```
Added value: +1
```

changedInput schema / properties / limit / type

Previous value: -"number"New value: +"integer"

addedInput schema / properties / online_status / enum

Added value: +[
+  "SUCCESS",
+  "WARNING",
+  "ERROR"
+]

addedInput schema / properties / reboot_required / enum
```
Added value: +[
+  "Yes",
+  "No"
+]
```

addedInput schema / properties / status / enum

Added value: +[
+  "Connected",
+  "Disconnected",
+  "Pending Uninstall"
+]

addedInput schema / properties / update_status / enum

Added value: +[
+  "SUCCESS",
+  "WARNING",
+  "ERROR"
+]

addedInput schema / properties / vulnerability_status / enum

Added value: +[
+  "SUCCESS",
+  "WARNING",
+  "ERROR"
+]

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 / items / items / properties

Added value: +{
+  "AD_organization_unit": {},
+  "AD_security_groups": {},
+  "CPU_model": {},
+  "CPU_name": {},
+  "CPU_size": {},
+  "MAC": {},
+  "NIC": {},
+  "OS": {},
+  "RAM": {},
+  "WiFi": {},
+  "added_via": {},
+  "address": {},
+  "agent_install_date": {},
+  "agent_version": {},
+  "architecture": {},
+  "comment": {},
+  "custom": {},
+  "device_name": {},
+  "disk": {},
+  "id": {},
+  "last_boot_time": {},
+  "last_seen": {},
+  "manufacturer": {},
+  "missing_updates": {},
+  "name": {},
+  "online_status": {},
+  "organization_id": {},
+  "platform": {},
+  "reboot_required": {},
+  "self": {},
+  "serial": {},
+  "status": {},
+  "subscription_status": {},
+  "type": {},
+  "update_status": {},
+  "user": {},
+  "video": {},
+  "vulnerabilities": {},
+  "vulnerability_status": {}
+}

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 readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, covering the safety profile. The description adds a genuinely useful non-annotation detail — the required view_endpoints permission — but says nothing about pagination behavior, defaults, or what the group membership result contains.

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?

Three short sentences, but sentence two duplicates sentence one almost verbatim and sentence one echoes the title. The permission note is the only sentence that earns its place; the rest is redundant padding rather than useful front-loading.

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?

Rich annotations, 100% schema coverage and a present output schema mean the structured data carries most of the burden. However, for a 17-parameter tool with filtering, sorting, pagination and a response_format default, the description never hints at that capability surface, leaving it thin for a first-pass selection decision.

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 all 17 parameters including the filter set and pagination controls are already documented in the schema. The description adds no semantics beyond naming group_id implicitly, making the baseline 3 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?

States a specific verb (List) and resource (endpoints scoped to a group), which is distinguishable from the sibling action1_list_endpoints and action1_search_endpoints by the group scoping. The second sentence largely restates the first, so it doesn't add scope detail beyond naming the group filter.

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?

No indication of when to use this versus action1_list_endpoints, action1_search_endpoints, or action1_get_group. The implicit usage is inferable from the name, but nothing actively routes the agent among near-identical siblings.

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

Deploy Server