Skip to main content
Glama
Sign In
Maintenant

Maintenant

by kOlapsis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

list_kubernetes_namespaces

Read-only

Retrieve Kubernetes namespaces across monitored clusters, optionally filtered by agent or cluster UUID, to identify available namespaces for monitoring.

Instructions

List Kubernetes namespaces known to maintenant across monitored clusters.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_kubernetes_namespaces"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_idNoFilter by agent/cluster UUID, or 'local'. Omit for all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.10.1

TDQS

A3.5/5.0
Behavior3/5

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

readOnlyHint=true already establishes the safety profile, so the description only needs to add context. It adds the useful fact that results span all monitored clusters, but says nothing about whether unmonitored or stale clusters appear, ordering, or result size for large fleets.

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?

One front-loaded sentence with no filler or repetition of the tool name. It is borderline under-specified rather than bloated, but every word earns its place.

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

Completeness4/5

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

For a single-optional-parameter read-only list tool with no output schema and full schema coverage, almost everything an agent needs is present. The only real gap is not stating what a namespace entry contains or how clusters are attributed in the response.

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% and the single optional agent_id parameter is fully documented in-schema including the 'local' sentinel and omit-for-all behavior. The description adds nothing beyond that, so the baseline 3 applies.

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?

Specific verb (List) plus resource (Kubernetes namespaces) with a scoping clause ('across monitored clusters'), which cleanly separates it from list_kubernetes_nodes/pods/workloads siblings. It never explicitly names an alternative, but the resource distinction is unambiguous.

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

Usage Guidelines3/5

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

Usage is only implied: an agent infers you call this to enumerate available namespaces before drilling into pods or workloads. There is no explicit when-to-use guidance, no mention of prerequisites (agent registration/monitoring) and no exclusions relative to the many other list_* siblings.

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

Deploy Server

Other Tools