action1-mcp-server

Get installed apps

action1_list_installed_software_data

Read-onlyIdempotent

Retrieve installed software inventory from managed endpoints and filter results by substring, organization, or live status to audit applications.

Instructions

Get installed apps. Gets a list of installed apps. Use parameters to filter out apps in the returned results. Perm: view_installed_software.

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.
`live_only`	No	Specify if you want to retrieve live results only.
`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: +{
+  "drilldown": {},
+  "drilldown_field": {},
+  "fields": {},
+  "id": {},
+  "self": {},
+  "type": {}
+}

First observedv0.5.0Jun 27, 2026

TDQS

C2.8/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 covered. The description adds one genuinely useful piece of context not in structured data: the required permission "view_installed_software" — an auth requirement worth surfacing. It says nothing about scope (org-wide vs endpoint), pagination behavior, or result volume, though.

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?

Short, but the first two sentences say the same thing twice and neither is front-loaded with anything the title does not already say. The permission note at the end is the only informative clause.

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 annotations, a full input schema and an output schema present, the structured fields cover most of what an agent needs. What remains missing is the one thing the description should supply: the scope of the listing relative to the many sibling inventory tools, and any note on pagination/auto_paginate interaction.

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% across all 10 parameters, so the schema carries the semantics for from, limit, cursor, filter, org_id, sortby, verbose, live_only, auto_paginate and response_format. The description's only parameter-adjacent remark is the generic note about filtering, which adds no meaning beyond the schema. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (list installed apps), but the first two sentences are near-duplicates of each other and of the title, adding nothing. There is no differentiation from closely related siblings such as action1_get_installed_software_endpoint, action1_software_inventory_for_endpoint, or action1_list_software_repository, so an agent cannot tell from the description which is the org-wide inventory listing.

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?

"Use parameters to filter out apps in the returned results" is a restatement of what parameters do, not guidance on when to choose this tool. No mention of when to use it versus the endpoint-scoped installed-software tools or the software repository listing, and no prerequisite context beyond the permission string.

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

Deploy Server