Skip to main content
Glama
artifacthub-mcp

artifacthub-mcp

by Ankur1911

security_report

Read-onlyIdempotent

Summarizes container image vulnerability scans for an Artifact Hub package version, showing severity counts, fix availability, and top critical or fixable findings.

Instructions

Vulnerability scan summary for a package version's container images (Trivy results published on Artifact Hub). Resolves the package id itself. Returns per-image counts by severity and how many have a fix, then the worst findings (critical first, fixable first) with installed and fixed versions. An absent report is explained, not an error.

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": {
      "kind": "<kind>",
      "repo": "<repo>",
      "name": "<name>"
    },
    "name": "security_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNoMaximum vulnerabilities to list.
kindYesPackage kind as used by Artifact Hub, e.g. 'helm' (charts), 'olm' (operators), 'krew', 'container', 'kyverno', 'opa', 'falco', 'backstage', 'keda-scaler', 'tekton-task', 'argo-template'.
nameYesPackage name within the repository, e.g. 'postgresql'.
repoYesRepository name on Artifact Hub (the 'repo' value from search_packages), e.g. 'bitnami'.
versionNoExact version. Omit for the latest version.
min_severityNoLowest severity to list.HIGH

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description goes beyond that by disclosing the data source (Trivy on Artifact Hub), the ordering of returned findings (critical first, fixable first), and the important error semantic that an absent report is explained rather than raised as an error.

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?

Four sentences, each carrying distinct payload: what it scans, the id resolution, the return shape and ordering, and the non-error absence behavior. Front-loaded with the resource and free of 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?

For a six-parameter read-only query with no output schema, the description supplies the return structure (per-image severity counts, fixable counts, worst findings with installed/fixed versions) and the absence behavior, which is everything an agent needs to call and interpret it correctly.

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 description coverage is 100%, so the baseline is 3 and the schema already documents each parameter. The description adds return-oriented meaning that clarifies intent behind min_severity and top ('worst findings', 'critical first, fixable first') and frames version selection as 'a package version', slightly exceeding the baseline.

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 names a specific verb+resource: a vulnerability scan summary of a package version's container images, sourced from Trivy data on Artifact Hub. That scope is unmistakably distinct from the sibling metadata tools (changelog, chart_values, package_details, search_packages), so an agent can select it 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 gives clear context for use and adds a prerequisite-eliminating note: 'Resolves the package id itself', telling the agent it need not pre-resolve an id. It stops short of stating when-not to use it or naming an explicit alternative, which keeps it out of 5 territory.

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