Skip to main content
Glama
mguttmann
by mguttmann

Listing missing updates

action1_list_updates
Read-onlyIdempotent

List missing updates with filters for approval status, severity, and customization to identify and manage pending patches.

Instructions

Listing missing updates. Gets a list of all missing updates. Use parameters to filter out updates in the returned results. 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.
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).
update_sla_end_dayNoThe maximum value of the remediation deadline in the SLA.
update_sla_start_dayNoThe minimum value of the remediation deadline in the SLA.

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 indicate safe read-only and idempotent behavior. The description adds permission requirements, which is useful context. However, it does not explain pagination, scoping, or what 'missing updates' entails.

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 somewhat redundant (first two sentences repeat the same idea). The permission list is useful but could be integrated more concisely. Overall, it is adequately sized but not optimally structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 17 parameters and the existence of an output schema, the description is too brief. It lacks explanation of the concept of 'missing updates,' how parameters interact, or typical usage patterns. The output schema partially compensates, but more context would improve agent selection.

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 coverage is 100%, so the schema documents all parameters. The description adds no additional meaning beyond 'use parameters to filter,' which does not enhance understanding of individual parameters.

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 tool lists all missing updates, but it does not distinguish from the sibling tool 'action1_list_missing_updates', which likely serves the same purpose.

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 explicit guidance on when to use this tool over alternatives like 'action1_list_missing_updates' or other list tools. The description only mentions using parameters to filter, but lacks context on appropriate use cases.

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