Skip to main content
Glama
Sign In

Opsphere — DevOps & SRE Intelligence

by io.opsphere.mcp-cursor
OverviewDiscussionsAdmin

Buscar pods de un cronjob

k8s_cronjob_pods
Read-only

Find pods related to a specific cronjob. Cronjobs create jobs, and jobs create pods. This tool finds all pods created by jobs of the specified cronjob. Useful when asked about a cronjob status and you need to see its running pods. Examples: "pods of the contentful-import cronjob", "show pods of the backup-daily cronjob".

Input Schema

NameRequiredDescriptionDefault
nsNoNamespace; alias: namespace
nameNoAlias of cronJobName
contextNokubectl --context opcional
profileNoAWS_PROFILE opcional para EKS/SSO
namespaceNoAlias of ns
context_idNoOptional explicit Connection Hub work context (ctx_*). Omit to use the conversation's active workspace; global Hub tools ignore it.
cronJobNameNoCronJob name; alias: name
environment_slugNoCloud catalog environment slug or alias (resolves AWS profile and kubectl context)

Output Schema

NameRequiredDescriptionDefault
okYes
dataYes
contractVersionYes
dataSchemaVersionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed18 schema fields changed
    • 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 / cronJob
      Added value: +{
+  "type": "string"
+}
    • 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"
-}
    • 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 / pods
      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 / 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: +[
+  "pods",
+  "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"
+]
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, so the safety profile is covered. The description adds a genuinely useful structural fact, that pods are reached transitively via jobs, but says nothing about whether pods of completed/failed historical jobs are included or what happens when jobs have been TTL-cleaned.

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-loaded purpose statement followed by the mechanism and then usage examples; almost every sentence earns its place. The two example utterances are somewhat redundant with the stated use case but aid routing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists and parameter meanings are in the schema, so the description needs only scope context. It omits which pods are returned (all jobs ever, or only current/recent) and does not mention that a namespace is needed despite zero required parameters, leaving real ambiguity for an 8-param tool.

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% across 8 parameters including aliases (ns/namespace, name/cronJobName), so the schema carries the parameter semantics. The description mentions no parameter names or constraint such as namespace being effectively required in practice.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 related to a specific cronjob') and usefully explains the ownership chain (cronjob -> job -> pod). It does not name or differentiate against the obvious sibling k8s_find_pod, so it stops short of a 5.

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 a clear triggering context ('when asked about a cronjob status and you need to see its running pods') plus two concrete example utterances. There is no when-not-to-use guidance pointing to k8s_find_pod or k8s_describe for other pod lookups.

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 toolsInspect
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