Skip to main content
Glama
kubesearch-mcp

kubesearch-mcp

by perfectra1n

Grep the always-warm pool of top repos

repo_grep_all
Read-onlyIdempotent

Search actual files across indexed home-ops repositories by substring without cloning; use returned handles to read or list files for follow-up.

Instructions

Substring-search the actual files of the most popular indexed home-ops repositories at once — no clone step needed. The server keeps these repos permanently cloned, so this covers every resource kind (Kustomizations, Ingress/HTTPRoute, ExternalSecrets, Talos configs, …), not just Helm values like grep_values. Hits are grouped by repo, most-starred first, and each group carries a handle you can pass straight to repo_read_file / repo_list_files / repo_grep for the follow-up. pool reports which repos were searchable: while pool.syncing is true and ready is below size the pool is still warming up, so an empty result is not final — retry after a short pause.

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

Input Schema

NameRequiredDescriptionDefault
globNoOptional path glob, e.g. '**/*.yaml' or 'kubernetes/apps/**'.
limitNoMax matching lines returned overall.
queryYesSubstring to search for, e.g. 'gatus.io/enabled' or 'kind: HTTPRoute'.
max_per_repoNoMax matching lines returned per repo.
case_sensitiveNoMatch case-sensitively.

Output Schema

NameRequiredDescriptionDefault
poolYes
queryYes
reposYes
truncatedYes
total_matchesYes
repos_searchedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.2.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already mark it read-only, idempotent and closed-world; the description adds behavior annotations can't capture — hits grouped by repo with most-starred first, per-group `handle` for follow-ups, and the crucial caveat that while `pool.syncing` is true an empty result is not final and should be retried.

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?

Three sentences, front-loaded with purpose, then result shaping, then the sync caveat in priority order. The first sentence is long with an em-dash aside, but every clause carries information an agent needs.

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?

Covers scope, result grouping, follow-up handles, and the warm-up/retry condition — the main failure mode an agent would otherwise misread as 'no matches'. Return-value detail is covered by the output schema, so nothing required for a correct call is missing.

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 description coverage is 100%, so query/glob/limit/max_per_repo/case_sensitive are already documented in the schema. The description adds no per-parameter syntax or defaults beyond that; the only extra detail is about the `pool` output field, not the inputs.

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: substring-search the files of top indexed home-ops repos without cloning. It explicitly distinguishes itself from `grep_values` by scope ('every resource kind ... not just Helm values'), so an agent can pick between the two without opening schemas.

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?

Gives clear usage context ('no clone step needed', all resource kinds) and names the follow-up tools `repo_read_file` / `repo_list_files` / `repo_grep` for drilling into a hit. It does not explicitly state when to prefer the single-repo `repo_grep` sibling over this pool-wide search, leaving one routing decision implicit.

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