Skip to main content
Glama
artifacthub-mcp

artifacthub-mcp

by Ankur1911

find_repositories

Read-onlyIdempotent

Search Artifact Hub package repositories by name to verify vendor status, repository kind, URL, and last tracking date; optionally filter by organization or kind.

Instructions

Find package repositories (publishers) by name, for example to see whether a vendor has a verified or official repo, which kind it hosts, its URL and when Artifact Hub last tracked it.

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

Input Schema

NameRequiredDescriptionDefault
orgNoRestrict to an organization name.
kindNoRestrict to one kind such as 'helm'.
limitNoMaximum repositories to return.
queryYesRepository name or part of it, e.g. 'bitnami'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/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 adds genuine value by disclosing the shape of the returned metadata (verification status, hosted kind, URL, last-tracked timestamp), but says nothing about result ordering, pagination, or behavior when the name matches many publishers.

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?

A single front-loaded sentence that puts the core action first and the motivating example second; every clause carries information. It is slightly long and comma-heavy but contains no filler.

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 compensates by naming the fields a caller can expect back, and all four parameters are documented in the schema. What is missing is minor: no note on default result count behavior or how multiple matching publishers are ordered.

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 the baseline is 3, and the description goes slightly beyond by framing the search as name-based publisher lookup, which clarifies the intent of 'query' beyond the schema's 'repository name or part of it'. The org and kind filters remain schema-only, 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 verb and resource — 'Find package repositories (publishers) by name' — and enumerates the attributes surfaced (verified/official status, kind, URL, last-tracked time). It implicitly separates repositories from the package-level siblings like search_packages and package_details, though it never names an alternative outright.

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?

The 'for example to see whether a vendor has a verified or official repo' clause gives a concrete motivating scenario, which implies when the tool is useful. However, there is no explicit when-not guidance, no mention of preferring search_packages for package-level lookups, and no stated prerequisites.

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