kubesearch-mcp

Search HelmReleases

kubesearch_search_releases

Read-onlyIdempotent

Search Flux HelmReleases and Argo Applications by chart name to find which public home-ops repos deploy them, with ranked results and links for full details.

Instructions

Search kubesearch.dev for Flux HelmReleases / Argo Applications by chart name (substring, case-insensitive). Mirrors the kubesearch.dev homepage search (e.g. 'cert-manager'). Results are grouped by chart source and ranked by how many public home-ops repos deploy them. Each result includes an id you can pass to kubesearch_get_release for full details, plus a kubesearch.dev link. Note: chart_source_url is a NORMALIZED grouping key (it matches kubesearch.dev's /hr/<id> grouping and intentionally collapses related registries, e.g. all bjw-s variants into 'oci://ghcr.io/bjw-s-labs/charts/'). For chartRef/OCIRepository releases the actual pullable chart is in source_urls (group) and each repo's source_url (+ source_tag); resolved_chart flags when the real chart name differs from chart.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Max number of chart groups to return.
`query`	Yes	Chart name or substring to search for, e.g. 'cert-manager', 'authentik', 'plex'.
`offset`	No	Pagination offset into the ranked results.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`query`	Yes
`shown`	Yes
`offset`	Yes
`results`	Yes
`has_more`	Yes
`search_url`	Yes
`total_matches`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedv1.2.0Sep 15, 2026
- removedOutput schema / properties / results / items / properties / resolved_chart / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / results / items / properties / resolved_chart / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / results / items / properties / top_repos / items / properties / chart_version / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / results / items / properties / top_repos / items / properties / chart_version / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / results / items / properties / top_repos / items / properties / namespace / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / results / items / properties / top_repos / items / properties / namespace / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / results / items / properties / top_repos / items / properties / resolved_chart / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / results / items / properties / top_repos / items / properties / resolved_chart / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / results / items / properties / top_repos / items / properties / source_kind / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / results / items / properties / top_repos / items / properties / source_kind / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / results / items / properties / top_repos / items / properties / source_tag / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / results / items / properties / top_repos / items / properties / source_tag / type
```
Added value: +[
+  "string",
+  "null"
+]
```
First observedv0.1.0Aug 7, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare readOnlyHint and idempotentHint, so the bar for extra value is high. The description adds substantial behavioral detail beyond annotations: case-insensitive substring matching, grouping by chart source, ranking by public repo usage, normalized `chart_source_url` behavior, and the `resolved_chart` flag. This gives the agent accurate expectations about how results are structured and why grouping keys may differ from actual pullable sources.

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?

The first sentence is front-loaded with the core purpose, followed by result-grouping context and the id-to-detail linkage. The second paragraph is a dense but necessary note about normalization, and every sentence earns its place with no filler. The structure is well organized and appropriately sized for the tool's complexity.

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?

The description is complete for an agent deciding whether to invoke this tool and how to interpret results. It covers search semantics, result grouping, ranking, how to follow up for full details, and the important normalization caveat. The output schema exists, so return-value details do not need to be restated, and annotations already cover safety and idempotency.

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. The description adds meaning beyond the schema by clarifying that `query` is a case-insensitive substring over chart names, giving concrete examples ('cert-manager', 'authentik'), and explaining that `chart_source_url` is a normalized grouping key rather than a literal registry URL. This supplements the schema's field descriptions usefully.

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 opens with a specific verb and resource: 'Search kubesearch.dev for Flux HelmReleases / Argo Applications by chart name.' It clearly differentiates from sibling tools by noting the returned `id` can be passed to `kubesearch_get_release` and by describing the homepage-search mirror, so an agent can distinguish it from `kubesearch_search_images` and other siblings.

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 description gives clear context for when to use the tool: searching chart names/substrings across HelmReleases and Argo Applications. It also names the follow-up tool (`kubesearch_get_release`) for full details, but it does not explicitly state when NOT to use this versus the sibling image-search tool, so it falls just short of full exclusion guidance.

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

Deploy Server