Opsphere — DevOps & SRE Intelligence

Buscar pod en todos los namespaces

k8s_find_pod

Read-only

Find pods whose name contains the required, non-empty pattern, scanning all namespaces in the cluster. Use k8s_cluster_summary for general cluster health; do not call this tool without a known pod/app pattern. Equivalent to: kubectl get pods -A | grep . Useful to locate in which namespace a pod is running when its location is unknown. Each result has a "name" (human-readable app name for display) and a "pod" (full technical pod name, used only as argument to k8s_logs/k8s_describe). ALWAYS use "name" when showing pods to the user. Examples: "where is the scheduler-cron pod", "in which namespace does storefront run", "find all pods containing algolia".

Input Schema

Name	Required	Description
`ns`	No	Optional namespace to avoid a cluster-wide scan; alias: namespace
`context`	No	kubectl --context opcional
`pattern`	Yes	Cadena no vacía que debe aparecer en el nombre del pod (obligatoria)
`profile`	No	AWS_PROFILE opcional para EKS/SSO
`namespace`	No	Alias of ns
`context_id`	No	Optional explicit Connection Hub work context (ctx_*). Omit to use the conversation's active workspace; global Hub tools ignore it.
`environment_slug`	No	Cloud catalog environment slug or alias (resolves AWS profile and kubectl context)

Output Schema

Name	Required	Description	Default
`ok`	Yes
`data`	Yes
`contractVersion`	Yes
`dataSchemaVersion`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed18 schema fields changedOct 26, 2026

changedOutput schema / properties / data / additionalProperties
```
Previous value: -trueNew value: +false
```
removedOutput schema / properties / data / properties / apiVersion
```
Removed value: -{
-  "type": "string"
-}
```
removedOutput schema / properties / data / properties / context
```
Removed value: -{
-  "type": "string"
-}
```
removedOutput schema / properties / data / properties / count
```
Removed value: -{
-  "type": "number"
-}
```

addedOutput schema / properties / data / properties / gaps

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

removedOutput schema / properties / data / properties / items

Removed value: -{
-  "items": {
-    "additionalProperties": true,
-    "properties": {},
-    "type": "object"
-  },
-  "type": "array"
-}

removedOutput schema / properties / data / properties / kind
```
Removed value: -{
-  "type": "string"
-}
```

addedOutput schema / properties / data / properties / matches

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "age": {
+        "type": "string"
+      },
+      "jobName": {
+        "type": "string"
+      },
+      "name": {
+        "type": "string"
+      },
+      "namespace": {
+        "type": "string"
+      },
+      "node": {
+        "type": "string"
+      },
+      "phase": {
+        "type": "string"
+      },
+      "pod": {
+        "type": "string"
+      },
+      "ready": {
+        "type": "string"
+      },
+      "restarts": {
+        "type": "integer"
+      }
+    },
+    "required": [
+      "name"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

removedOutput schema / properties / data / properties / metadata

Removed value: -{
-  "$ref": "#/properties/data/properties/items/items"
-}

removedOutput schema / properties / data / properties / namespace
```
Removed value: -{
-  "type": "string"
-}
```
addedOutput schema / properties / data / properties / partial
```
Added value: +{
+  "type": "boolean"
+}
```
addedOutput schema / properties / data / properties / query
```
Added value: +{
+  "type": "string"
+}
```

removedOutput schema / properties / data / properties / status

Removed value: -{
-  "$ref": "#/properties/data/properties/items/items"
-}

addedOutput schema / properties / data / properties / truncated
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / data / properties / warnings

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / data / required

Added value: +[
+  "matches",
+  "partial",
+  "truncated",
+  "warnings",
+  "gaps"
+]

addedOutput schema / properties / dataSchemaVersion

Added value: +{
+  "const": 2,
+  "type": "number"
+}

changedOutput schema / required

Previous value: -[
-  "contractVersion",
-  "ok",
-  "data"
-]New value: +[
+  "contractVersion",
+  "dataSchemaVersion",
+  "ok",
+  "data"
+]

First observedOct 15, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare read-only, non-destructive, non-open-world, so the safety profile is covered; the description adds real value beyond that with the kubectl equivalence (kubectl get pods -A | grep <pattern>), the cluster-wide scan cost implication, and the critical result-field contract ('name' for display, 'pod' only as an argument to k8s_logs/k8s_describe). It stops short of noting match semantics edge cases (case sensitivity) or result-volume expectations, small but real gaps.

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?

Front-loads the core action and scope, then the routing rule, then the output-field contract — good ordering with no filler sentences. It runs slightly long with the trailing example list, but each element serves disambiguation or correct tool chaining.

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 7-parameter, fully schema-documented, output-schema-backed read tool, the description covers purpose, exclusions, equivalence, and — unusually — how to consume the returned fields and pass them to k8s_logs/k8s_describe. Nothing an agent needs to call it correctly or use the results 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 every parameter including ns, context, profile, and the alias namespace is already documented in the schema. The description only restates that the pattern is required and non-empty and that the scan is cluster-wide, adding no syntax or matching details beyond structured data. Baseline 3 applies.

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 ('Find pods whose name contains the required, non-empty pattern') plus scope ('scanning all namespaces in the cluster'). It explicitly distinguishes itself from k8s_cluster_summary, so an agent can tell the two apart without opening either schema.

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?

Gives an explicit when-to-use ('locate in which namespace a pod is running when its location is unknown'), an explicit when-not ('do not call this tool without a known pod/app pattern'), and names the alternative for the other case (k8s_cluster_summary). Concrete example queries further anchor selection.

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

All Opsphere — DevOps & SRE Intelligence tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?