Skip to main content
Glama

search

Read-only

Search Kubernetes resources by content or term match across all object types. Locate unknown resources using free-text queries and optional modifiers like kind, namespace, label, or image.

Instructions

Find resources by content/term match when you do not know which object contains a string, config key, env ref, image, label/annotation value, ConfigMap data, CRD field, or status message. Tokens are AND'd. Secret content is intentionally NOT indexed — Secret names match by metadata, but data values won't appear in snippets to avoid leaking secret material through search results. Examples: readinessProbe user-service, image:flagd, kind:Pod label:app=cart error. Modifiers such as kind:Pod, ns:foo, label:app=bar, and image:redis narrow a term match; modifier-only queries are enumeration, so use list_resources when you already know the kind/namespace. Returns ranked hits with snippets and summaryContext. Use CEL filter for structural predicates. Searches typed kinds plus warmed CRDs; cold CRDs need list_resources first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYessearch query for unknown resources or broad content scans. Free tokens AND'd. Matches identity plus searchable object content. Examples: adServiceFailure, kind:NetworkChaos delay, kind:ConfigMap flagd, image:flagd. Modifiers: kind:Pod, kind:NetworkChaos, ns:foo, label:k=v, image:redis
limitNomax hits returned (default 50, max 500)
includeNoper-hit detail: summary (default), raw, or none
filterNooptional CEL boolean expression run against each candidate K8s object. Bindings: kind, apiVersion, metadata, spec, status, labels, annotations. Use has(x.y) before optional fields. Examples: 'kind == "Pod" && status.phase == "Failed"', 'labels["app"] == "cart"', 'has(status.readyReplicas) && status.readyReplicas == 0'
contextNoper-hit context: default attaches summaryContext (managedBy + health + issueCount) for suspect ranking; 'none' returns bare hits
Behavior5/5

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

Annotations declare readOnlyHint=true, which is consistent with a search operation. The description adds critical behavioral details: tokens are AND'd, Secret data is not indexed, returns ranked hits with snippets and summaryContext, searches typed kinds and warmed CRDs (cold CRDs need list_resources first). 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?

The description is well-structured with a clear first sentence defining purpose, followed by exclusions, examples, and additional notes. Every sentence adds meaningful information without redundancy. It is appropriately concise for the complexity of the tool.

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?

Without an output schema, the description explains what the tool returns (ranked hits with snippets and summaryContext). It covers edge cases (Secrets not indexed, cold CRDs need list_resources) and examples. The tool is a search for unknown resources, and the description provides complete context for an agent to use it correctly.

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 description coverage is 100%, so baseline is 3. The description adds value beyond schema by explaining token AND behavior, modifier usage, Secret exclusion, and context options. It enhances understanding of how parameters work in practice, justifying a 4.

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 clearly states the tool finds resources by content/term match when the agent doesn't know which object contains a string. It distinguishes from list_resources by specifying that modifier-only queries (enumerations) should use list_resources. Examples and exclusions (Secret content not indexed) further clarify the purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly states when to use (when you don't know which object contains a string) and when not to use (modifier-only queries should use list_resources). It provides examples of valid queries and mentions using CEL filter for structural predicates, giving clear usage guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/skyhook-io/radar'

If you have feedback or need assistance with the MCP directory API, please join our Discord server