kubesearch-mcp

Grep HelmRelease values

kubesearch_grep_values

Read-onlyIdempotent

Search real-world HelmRelease and Application values by substring to find config key or value examples. Get matched key path, snippet, and source file.

Instructions

Full-text grep across the Helm spec.values of every indexed HelmRelease/Application (substring match). Great for finding real-world examples of a config key or value, e.g. 'cert-manager.io', 'nodeSelector', 'gatus'. Returns the matched key path, a snippet, and the source file. Mirrors the kubesearch.dev /grep search.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Max number of matching files to return.
`query`	Yes	Substring to grep for in values (keys or values), e.g. 'cert-manager.io'.
`offset`	No	Skip this many matches (results are ranked by repo stars).
`case_sensitive`	No	Match case-sensitively.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`query`	Yes
`shown`	Yes
`offset`	Yes
`results`	Yes
`grep_url`	Yes
`has_more`	Yes
`total_files`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedv1.2.0Sep 15, 2026
- removedOutput schema / properties / results / items / properties / chart / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / results / items / properties / chart / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / results / items / properties / matched_key / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / results / items / properties / matched_key / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / results / items / properties / repo / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / results / items / properties / repo / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / results / items / properties / stars / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / results / items / properties / stars / type
```
Added value: +[
+  "number",
+  "null"
+]
```
First observedv0.1.0Aug 7, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already establish read-only and idempotent behavior. The description adds meaningful context by specifying the scope ('every indexed HelmRelease/Application'), the substring-match nature, and the result shape (matched key path, snippet, source file). No contradictions with annotations.

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 concise sentences front-load the core operation, provide concrete examples, and mention the output format. Every sentence earns its place without unnecessary detail.

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 straightforward grep tool with full schema coverage, annotations, and an output schema, the description covers scope, semantics, use cases, and result content. Nothing essential is missing for an agent to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema fully documents query, limit, offset, and case_sensitive. The description adds useful examples and clarifies the query targets config keys/values, but does not materially expand parameter semantics beyond the schema.

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 uses a specific verb ('grep') and resource ('Helm spec.values of every indexed HelmRelease/Application'), clearly distinguishing this from file-based repo grep tools. It also states the substring-match behavior and the return payload, leaving no ambiguity about what the tool does.

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 it: finding real-world examples of config keys or values, with concrete examples. It does not explicitly name alternative tools or exclusion cases, but the Helm-values-specific scope makes the intended use obvious.

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

Deploy Server