Skip to main content
Glama
artifacthub-mcp

artifacthub-mcp

by Ankur1911

search_packages

Read-onlyIdempotent

Search Artifact Hub packages by free text and filters, returning paged, compact rows with package metadata, publisher trust flags, and vulnerability summaries for further exploration.

Instructions

Search Artifact Hub packages by free text (websearch syntax: quoted phrases, -exclusions, 'or'). Returns compact rows with kind, repo, name, version, app version, stars, last update, publisher trust flags and a non-zero vulnerability summary, plus the total count and next_offset for paging. Use the kind/repo/name values with the other tools.

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": {
      "query": "<query>"
    },
    "name": "search_packages"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgNoRestrict to an organization name, e.g. 'bitnami' or 'prometheus-community'.
kindNoRestrict to one kind such as 'helm' or 'olm'. Omit to search every kind.
sortNoResult order.relevance
limitNoRows to return.
queryYesSearch text, e.g. 'postgresql', 'ingress controller', '"cert manager"'.
offsetNoRows to skip, for paging.
officialNoOnly packages from official repositories (published by the software's own maintainers).
include_deprecatedNoInclude deprecated packages (hidden by default).
verified_publisherNoOnly packages from verified publishers.

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 readOnly/openWorld/idempotent, yet the description still adds genuine value: the exact returned row fields, the inclusion of a non-zero vulnerability summary, publisher trust flags, and the presence of total count plus next_offset for paging. It does not mention rate limits or result-window caps beyond what the schema's limit maximum implies.

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?

Two dense sentences: the first front-loads purpose plus the query grammar, the second covers return shape, pagination, and handoff. No filler or restated parameter lists.

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 9-parameter search tool with no output schema, the description supplies the critical missing piece — what a row contains and how to page — while the schema fully covers filter semantics. An agent has everything needed to call it and to use its output downstream.

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 would be 3, but the description adds meaning the schema lacks: the free-text query supports websearch syntax with exclusions and boolean 'or'. Other parameters (org, kind, sort, official, include_deprecated) are left entirely to the schema, which documents them adequately.

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 ('Search Artifact Hub packages by free text') and even specifies the query grammar (quoted phrases, -exclusions, 'or'), which no sibling name implies. The closing sentence routes the agent onward with kind/repo/name keys, making the distinction from drill-down siblings like package_details clear.

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?

The final sentence explicitly establishes the workflow: use this tool first, then feed the returned kind/repo/name into the other tools. It stops short of naming an alternative search path (e.g. find_repositories) or saying when not to use this tool, so no exclusion is stated.

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