Skip to main content
Glama

listSoftwarePackages

List and filter Mallory software packages, returning lean summaries as {items,total,offset,limit}. Each item includes: package name, ecosystem, description, known configurations, supply-chain compromise evidence, and upstream OpenSSF Scorecard assessment (0–10, higher is better). Filter prefixes: name:, uuid:. Sort by created_at, updated_at, last_compromised_at, compromise_evidence_count, or openssf_score (unknown last). Field operators append to a field name with __: strings support __neq, __in, __not_in, __like, __ilike; numbers support __gt, __gte, __lt, __lte. Timestamps (created_at, updated_at) support __gte and __lt ONLY — there is no __gt, __lte, or bare equality on them, so express a range as the half-open created_at__gte=&created_at__lt=. Pass an item's identifier to getSoftwarePackage for the full detail object.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "listSoftwarePackages"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoField to sort by (see this tool's sort fields).
limitNoMax items to return (1-100, default 25).
orderNoSort order (default: desc).
filterNoPrefix filter string (see this tool's filter prefixes). No prefix = default name/text search.
offsetNoItems to skip, for pagination.
fieldFiltersNoAdvanced structured filters as a map of query-param name -> value. Use a bare field for exact match, or a field__operator key for ranges/sets. Field operators append to a field name with `__`: strings support __neq, __in, __not_in, __like, __ilike; numbers support __gt, __gte, __lt, __lte. Timestamps (created_at, updated_at) support __gte and __lt ONLY — there is no __gt, __lte, or bare equality on them, so express a range as the half-open created_at__gte=<start>&created_at__lt=<end>.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

No annotations are supplied, so the description must carry the burden and largely does: it enumerates the returned item fields (compromise evidence, OpenSSF score with its 0–10 direction and 'unknown last' sort behavior) and the response envelope. It does not state permission requirements or rate limits, and read-only-ness is only implied by "List".

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?

One dense paragraph, front-loaded with purpose and return shape before the operational rules. It earns most of its words, though the operator matrix is repeated almost verbatim from the fieldFilters schema description, which is wasted length.

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

Completeness4/5

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

With 6 optional params, a nested fieldFilters object, and no output schema, the description does the necessary work: response envelope, item contents, filter syntax, sortable fields, and the handoff to getSoftwarePackage. Only access/permission behavior and result-set limits are left unspecified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds real meaning the schema only gestures at: it supplies the actual filter prefixes (name:, uuid:, bare = default name/text search) and the concrete sortable fields that the schema refers to only as "this tool's sort fields". It also reiterates the timestamp half-open range constraint, which is somewhat redundant with 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 opens with a specific verb and resource ("List and filter Mallory software packages") and states the return envelope {items,total,offset,limit}. The closing sentence names getSoftwarePackage as the tool for full detail, so an agent can separate list from detail without opening the schema.

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

Usage Guidelines4/5

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

It routes clearly to getSoftwarePackage when a single full record is wanted, and documents which filters/sorts are valid. It stops short of stating when *not* to use this tool (e.g., prefer a different list endpoint for cross-entity search), but the list-vs-detail split is explicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources