Skip to main content
Glama
Sign In
KubeCraft MCP Server

KubeCraft MCP Server

by cloudcrafttech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

List Flux HelmReleases

flux_list_helmreleases

List Flux HelmReleases in any namespace, displaying ready status, chart name, version, release name, and values summary for quick cluster state inspection.

Instructions

List Flux HelmReleases with ready status, chart name, version, release name, and values summary.

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

Input Schema

NameRequiredDescriptionDefault
namespaceNoNamespace (omit for all namespaces)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations, the description should disclose behavioral traits. It implies read-only listing but doesn't explicitly state safety, non-destructiveness, or any constraints like pagination or rate limits. The 'values summary' phrase is vague.

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 a single, concise sentence that front-loads the main action and lists the output fields. No unnecessary words; every part adds value.

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 simple list tool with one optional parameter and no output schema, the description covers the main purpose and output fields adequately. It could clarify 'values summary' but is otherwise sufficient.

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?

The input schema already covers the single parameter 'namespace' with clear description. The tool description adds no additional meaning beyond what the schema provides. Schema description coverage is 100%, so baseline is 3.

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 lists Flux HelmReleases and specifies the information included: ready status, chart name, version, release name, and values summary. This distinguishes it from sibling tools like flux_list_kustomizations or flux_list_sources.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives (e.g., helm_get_values for detailed values, or flux_list_kustomizations for other resources). No mention of when not to use it or prerequisites.

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