action1-mcp-server

List managed endpoints (cursor-paginated)

action1_list_endpoints

Read-onlyIdempotent

List endpoints using server-side filters such as status, online status, OS, and reboot requirement. For endpoint counts, use the summary tool instead.

Instructions

List endpoints with server-side filters (status, online_status, os, reboot_required, …). For counts, use action1_endpoints_summary instead.

Input Schema

Name	Required	Description
`os`	No	Filter by operating system name.
`limit`	No	Max items.
`cursor`	No	Pagination cursor.
`fields`	No	API field-set: *, missing_updates, vulnerabilities.
`filter`	No	Case-insensitive substring; an endpoint matches when any field contains it.
`org_id`	No	Org UUID.
`sortby`	No	Sort key (e.g. name, last_seen).
`status`	No	Filter by status: Connected, Disconnected, Pending Uninstall.
`page_size`	No	Upstream page size.
`projection`	No	Client projection: bare (default), compact, full.
`reset_cache`	No	Bypass cache for fresh page.
`online_status`	No	Filter by online status: SUCCESS, WARNING, ERROR.
`update_status`	No	Filter by update status: UNDEFINED, SUCCESS, WARNING, ERROR.
`reboot_required`	No	Filter by reboot-required: Yes or No.
`response_format`	No	Output format. Default markdown.
`vulnerability_status`	No	Filter by vulnerability status: UNDEFINED, SUCCESS, WARNING, ERROR.

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.

Changed12 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 / filter / description

Previous value: -"Action1 filter expr (e.g. status=='Connected')."New value: +"Case-insensitive substring; an endpoint matches when any field contains it."

changedInput schema / properties / online_status / description

Previous value: -"Filter by online status."New value: +"Filter by online status: SUCCESS, WARNING, ERROR."

changedInput schema / properties / os / description

Previous value: -"Filter by OS substring."New value: +"Filter by operating system name."

changedInput schema / properties / reboot_required / description

Previous value: -"Filter by reboot-required."New value: +"Filter by reboot-required: Yes or No."

changedInput schema / properties / reboot_required / enum

Previous value: -[
-  "yes",
-  "no"
-]New value: +[
+  "Yes",
+  "No",
+  "yes",
+  "no"
+]

changedInput schema / properties / status / description

Previous value: -"Filter by status (Connected/Disconnected)."New value: +"Filter by status: Connected, Disconnected, Pending Uninstall."

changedInput schema / properties / update_status / description

Previous value: -"Filter by update status."New value: +"Filter by update status: UNDEFINED, SUCCESS, WARNING, ERROR."

changedInput schema / properties / vulnerability_status / description

Previous value: -"Filter by vulnerability status."New value: +"Filter by vulnerability status: UNDEFINED, 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 / propertyNames
```
Added value: +{
+  "type": "string"
+}
```

First observedv0.5.0Jun 27, 2026

TDQS

A3.9/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, so the safety profile is fully covered. The description adds that filters are applied server-side, which is useful, but says nothing about caching (reset_cache), cursor paging semantics, or how projection changes payload size.

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?

Two short sentences with zero filler, purpose and the filter capability front-loaded, and the alternative routing instruction second. Every clause earns its place.

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 a full output schema and rich annotations, the description need not explain return values or safety, and it correctly covers purpose plus the primary alternative. It is slightly thin for a 16-parameter tool in not distinguishing itself from the other endpoint-listing siblings or explaining default pagination behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% with 16 well-documented parameters, so the baseline is 3. The description supplies extra meaning beyond the schema by labeling the status/os/reboot_required inputs as server-side filters, telling the agent these narrow the query rather than being post-filtered client-side.

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) plus the meaningful qualifier that filtering happens server-side, and names the sibling tool to use for counts. It does not differentiate itself from action1_search_endpoints, which an agent could easily confuse with this tool.

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

Usage Guidelines4/5

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

Gives one explicit routing rule: for counts, use action1_endpoints_summary instead. There is no guidance on when to prefer this over action1_search_endpoints or action1_list_group_contents, so the alternative-selection story is only partially covered.

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

Deploy Server