action1-mcp-server

Get installed apps on a specific endpoint

action1_get_installed_software_endpoint

Read-onlyIdempotent

Retrieve a list of installed applications on a specific endpoint by ID to audit software inventory or troubleshoot installations.

Instructions

Get installed apps on a specific endpoint. Gets a list of installed apps on an endpoint specified by its ID. Perm: view_installed_software, 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.
`response_format`	No	Output format. Default markdown.

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: +{
+  "fields": {},
+  "id": {},
+  "last_refresh": {},
+  "response_type": {},
+  "self": {},
+  "type": {}
+}

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 readOnly, idempotent, non-destructive, openWorld behavior, so the safety profile is covered. The description adds genuinely useful auth context (required permission scopes), but says nothing about pagination behavior despite ten paging-related parameters, and does not hint at result volume for an endpoint with many apps.

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 first two sentences are near-duplicates ('Get installed apps on a specific endpoint' vs 'Gets a list of installed apps on an endpoint specified by its ID'), so half the text restates itself. The permission note is front-loaded and useful, but the redundancy costs it.

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?

With a full input schema, an output schema, and rich annotations, the description needs to carry little — but the most valuable missing piece is disambiguation from sibling inventory/installed-software tools. Adequate but leaves the agent to infer selection among similar siblings.

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% and all ten parameters carry inline descriptions (from/limit/cursor, filter, sortby, verbose, response_format), so baseline 3 applies. The description adds no interpretation of what 'filter' matches or how paging interacts with auto_paginate beyond what the schema states.

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 with scope narrowed to one endpoint ID, so the agent knows exactly what is returned. However, it never differentiates from close siblings like action1_list_installed_software_data or action1_software_inventory_for_endpoint, which an agent choosing among 130+ tools would need.

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 conditional information is the permission requirement (view_installed_software, view_endpoints). There is no statement of when to prefer this over the org-wide installed-software listing or the endpoint inventory tool, and no exclusions or prerequisites beyond the perm names.

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

Deploy Server