Skip to main content
Glama
mguttmann
by mguttmann

Listing updates for a package

action1_get_update_package
Read-onlyIdempotent

List available updates for a specific package by providing its ID. Filter, sort, and paginate results to find the updates you need.

Instructions

Listing updates for a package. Gets a list of updates available for a package specified by its ID. Perm: approve_updates, view_dashboards, manage_automations.

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.
package_idYesProvide a specific package ID.
only_latestNoSpecify if you want to exclude superseded updates. By default, 'yes'.
auto_paginateNoWalk all pages.
approval_statusNoSpecify the update status.
response_formatNoOutput format. Default markdown.
security_severityNoSpecify the severity level, e.g., security_severity=-Critical (for all non-critical).

Output Schema

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

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

Annotations already provide readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, indicating safe, read-only behavior. The description adds value by listing the specific permissions needed, which goes beyond the annotations.

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?

The description is very concise at two sentences, with no unnecessary words. The first sentence front-loads the core purpose. However, it could be slightly more efficient by combining the two sentences.

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 complexity (16 parameters, rich annotations, output schema), the description is minimal. It states the basic task but doesn't elaborate on the nature of 'updates', pagination, or filtering options. Output schema fills some gaps, but more context would help the agent.

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?

The input schema has 100% description coverage for all 16 parameters, so the schema already documents parameter meaning. The description adds no additional information beyond mentioning the required 'package_id' implicitly. Baseline 3 is appropriate.

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 states the verb 'Gets a list' and the resource 'a package', specifying the action. However, it does not differentiate from sibling tools like list_updates or list_missing_updates, missing a chance to clarify uniqueness.

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?

It lists required permissions, which helps the agent understand authorization requirements. However, there is no guidance on when to use this tool versus alternatives, nor any exclusions or when not to use it.

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