Skip to main content
Glama
artifacthub-mcp

artifacthub-mcp

by Ankur1911

changelog

Read-onlyIdempotent

Fetch release notes for an Artifact Hub package, optionally limiting to versions newer than your current one to show the upgrade delta; each entry includes dates, security flags, and trimmed changes.

Instructions

Release notes for a package. Pass since_version to get only the releases newer than the version you run (the upgrade delta); otherwise the newest entries are returned. Each entry has the date, a security-update flag and trimmed change lines. Not every publisher provides a changelog; that case is reported.

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": "changelog"
  }
}

Input Schema

NameRequiredDescriptionDefault
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'.
limitNoMaximum entries to return.
since_versionNoVersion you are on now; returns only newer entries.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/idempotent, so the bar is lower, and the description still adds real value: the shape of each entry (date, security-update flag, trimmed change lines) and the explicit failure mode when a publisher provides no changelog. It does not discuss rate limits or how 'trimmed' lines are produced, keeping it short of a 5.

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, front-loaded with the resource, then the mode switch, then the return shape and the no-changelog caveat. No filler or restated title.

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 no output schema, the description usefully describes the returned entry fields and the empty-changelog case, which is what an agent needs to interpret results. Minor gaps remain around how limit interacts with since_version and what 'trimmed' means, but nothing blocking.

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; the description earns an extra point by explaining the intent behind since_version ('the version you are on now', 'the upgrade delta') rather than just restating it. limit and the required kind/repo/name are left entirely to the schema, which is acceptable given full coverage.

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?

States a specific resource and action: 'Release notes for a package', and immediately clarifies the two modes (delta via since_version vs newest entries). It is clearly distinct from siblings like package_details or chart_values by resource, though it never names an alternative explicitly.

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?

Gives solid guidance on when to pass since_version ('the version you run', 'the upgrade delta') versus omitting it, and warns that some publishers have no changelog. However, it offers no guidance on choosing this tool over package_details or security_report, leaving sibling selection to inference.

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