action1-mcp-server

List Software Repository packages

action1_list_software_repository

Read-onlyIdempotent

List Software Repository packages across the enterprise, with filters for platform, custom or builtin status, name, and version, plus pagination to retrieve results in manageable pages.

Instructions

List Software Repository packages. Gets a list of Software Repository packages for the entire enterprise. Perm: view_software_repository.

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.
`custom`	No	Specify if the package is custom (yes) or builtin (no).
`fields`	No	Add FIELDS parameter to query extended data.
`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.
`builtin`	No	Specify if the package is builtin (yes) or custom (no).
`verbose`	No	Skip per-item compactor.
`platform`	No	platform
`match_name`	No	Provide the software name to search for.
`auto_paginate`	No	Walk pages until limit or the size budget; then continue with next_cursor.
`match_version`	No	Provide the software version to search for.
`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.

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 / 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 / platform / enum

Added value: +[
+  "Windows",
+  "Mac",
+  "Linux"
+]

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": {},
+  "name": {},
+  "scope": {},
+  "self": {},
+  "status": {},
+  "type": {},
+  "vendor": {},
+  "versions": {}
+}

First observedv0.5.0Jun 27, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description's genuine addition is the required permission (view_software_repository), which is real auth context an agent cannot get from annotations. It says nothing about pagination behavior or result volume despite 15 params including cursor and auto_paginate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the action and scope. The first two sentences restate each other ('List Software Repository packages' / 'Gets a list of Software Repository packages'), a small redundancy but not harmful.

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?

An output schema exists and every parameter is documented, so the description needn't explain returns. Still, for a 15-parameter enterprise-wide listing tool, an agent would benefit from a note on pagination/volume expectations and on how the enterprise scope interacts with the org_id parameter — neither is addressed.

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 15 parameters are documented in-schema (including filter, match_name/match_version, platform, fields, verbose). Baseline 3 — the description adds no parameter meaning, but nothing is missing from the schema either.

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 (list Software Repository packages) plus the scope: 'for the entire enterprise.' That scope note distinguishes it from sibling get_software_repository_package (single item) without naming it explicitly, so the differentiation is implied rather than stated.

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 guidance on when to choose this over siblings such as action1_get_software_repository_package, action1_list_updates, or action1_list_installed_software_data — which are the natural confusion points in this crowded list. The 'entire enterprise' scope is the only cue, and it is not framed as a selection rule.

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

Deploy Server