action1-mcp-server

Get missing updates for an endpoint

action1_list_endpoint_missing_updates

Read-onlyIdempotent

Retrieve and filter missing software updates for a specific endpoint. Narrow the list by severity or approval status to manage patch cycles and maintain endpoint security.

Instructions

Filtered/paginated variant of action1_list_missing_updates (curated). Use for severity/approval_status/sortby filtering. Get missing updates for an endpoint. Obtains a list of missing software updates for a specific endpoint. Perm: view_endpoints.

Input Schema

Name	Required	Description
`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.
`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.
`verbose`	No	Skip per-item compactor.
`endpoint_id`	Yes	Provide an endpoint ID.
`auto_paginate`	No	Walk pages until limit or the size budget; then continue with next_cursor.
`approval_status`	No	Specify the update status.
`response_format`	No	Output format. Default markdown.
`security_severity`	No	Specify the severity level, e.g., security_severity=-Critical (for all non-critical).

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.

Changed11 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"

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: +{
+  "builtin": {},
+  "description": {},
+  "id": {},
+  "internal_notes": {},
+  "kb_number": {},
+  "name": {},
+  "optional": {},
+  "organization_ids": {},
+  "reboot_needed": {},
+  "recommended": {},
+  "scope": {},
+  "self": {},
+  "size": {},
+  "status": {},
+  "type": {},
+  "update_type": {},
+  "vendor": {},
+  "versions": {}
+}

First observedv0.5.0Jun 27, 2026

TDQS

A3.8/5.0

Behavior4/5

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

The annotations already declare read-only, idempotent, open-world, and non-destructive behavior, so the description does not need to restate safety. It adds useful context by naming the required permission (view_endpoints) and noting that this is a filtered/paginated variant; it does not discuss pagination behavior in detail, but the output schema and parameter descriptions cover much of that.

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?

The text is short, but it repeats the same purpose multiple times: 'Get missing updates for an endpoint' and 'Obtains a list of missing software updates for a specific endpoint.' The opening variant reference is front-loaded, but the description could be tighter and less redundant.

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?

For a 12-parameter read-only listing tool with a 100% documented schema, annotations, and an output schema, the description supplies the important scope (endpoint-specific), filtering guidance, and permission requirement. It need not explain return values because an output schema exists.

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 12 parameters thoroughly. The description mentions the key filtering use cases (severity, approval_status, sortby) but adds little beyond what the schema and parameter descriptions already provide, so the baseline 3 applies.

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 description clearly identifies a specific verb and resource: obtaining missing software updates for a specific endpoint. It also distinguishes itself as a filtered/paginated variant of action1_list_missing_updates, though the purpose is repeated several times rather than stated once crisply.

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?

It gives explicit guidance to use this tool for severity, approval_status, or sortby filtering, and implicitly positions it against the base action1_list_missing_updates. It does not state when not to use it, but the alternative relationship is clear enough for selection.

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

Deploy Server