Skip to main content
Glama

getSoftwarePackage

Fetch a single Mallory software package by identifier (a package UUID) and return its full detail. Returns: package name, ecosystem, description, known configurations, supply-chain compromise evidence, and upstream OpenSSF Scorecard assessment (0–10, higher is better). If you only have a name or search terms, call listSoftwarePackages first to find the exact identifier. For relationship pivots (e.g. related malware or attack patterns) and advanced cross-entity queries, use queryApi.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "identifier": "<identifier>"
    },
    "name": "getSoftwarePackage"
  }
}

Input Schema

NameRequiredDescriptionDefault
identifierYesThe software package identifier — a package UUID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it enumerates the return payload (name, ecosystem, description, known configurations, compromise evidence, OpenSSF Scorecard with the 0–10 scale and direction). It omits permission/auth requirements and what happens for an unknown or malformed UUID, which are the remaining behavioral gaps.

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

Conciseness5/5

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

Three tight sentences, each doing distinct work: what it fetches, what comes back, and where to go otherwise. The purpose and return contents are front-loaded with zero filler.

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

Completeness5/5

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

No output schema exists, so the description must describe the return value — it does so explicitly, including the Scorecard scale. Combined with the identifier-resolution guidance and sibling routing, an agent has everything needed to invoke it correctly.

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% and the single parameter's description already says it is a package UUID, so the description mostly restates the schema. Its added value is the procedural hint that a name must first be resolved via listSoftwarePackages, not a deeper format or example of the identifier itself.

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?

States a specific verb and resource ('Fetch a single Mallory software package'), pins the identifier type ('a package UUID'), and promises 'full detail'. An agent can immediately distinguish it from listSoftwarePackages (enumeration by name/terms) and queryApi (relationship pivots).

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

Usage Guidelines5/5

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

Gives explicit routing rules: if you only have a name or search terms, call listSoftwarePackages first to resolve the exact identifier; for relationship pivots or cross-entity queries, use queryApi instead. Both the when-to-use and the when-to-use-something-else conditions are spelled out.

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