Skip to main content
Glama
mguttmann
by mguttmann

List Software Repository packages

action1_list_software_repository
Read-onlyIdempotent

Retrieve a list of software repository packages across the enterprise, with filters for name, version, platform, and pagination.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fromNoProvide the number of the first record to be returned.
limitNoSet the maximum number of items to be returned (the page size).
cursorNoPagination cursor.
customNoSpecify if the package is custom (yes) or builtin (no).
fieldsNoAdd FIELDS parameter to query extended data.
filterNoProvide a case-insensitive substring to filter and narrow down returned results (i.e., if...
org_idNoOrg UUID.
sortbyNoDefine the sorting order by a certain field.
builtinNoSpecify if the package is builtin (yes) or custom (no).
verboseNoSkip per-item compactor.
platformNoplatform
match_nameNoProvide the software name to search for.
auto_paginateNoWalk all pages.
match_versionNoProvide the software version to search for.
response_formatNoOutput format. Default markdown.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteNo
countYes
itemsYes
totalNo
has_moreNo
next_cursorNo
Behavior3/5

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

Annotations already cover readOnly, idempotent, and non-destructive hints. The description adds the permission requirement but does not elaborate on pagination or open world behavior beyond what annotations indicate.

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 description is short but contains redundancy (first sentence repeats title). It is front-loaded but could be more concise.

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?

Given the 15 parameters and available schema descriptions, the description is adequate but minimal. It lacks context on how parameters affect results (e.g., filtering, pagination).

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 description need not add parameter details. It does not provide additional meaning beyond the schema.

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

Purpose5/5

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

The description states 'List Software Repository packages' with scope 'for the entire enterprise,' clearly differentiating from sibling tools like get_software_repository_package. The permission requirement is also specified.

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

Usage Guidelines3/5

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

The description implies usage for listing all enterprise packages but does not provide explicit guidance on when to use alternatives (e.g., search or get_software_repository_package) or specify exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mguttmann/action1-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server