Skip to main content
Glama
Sign In
KubeCraft MCP Server

KubeCraft MCP Server

by cloudcrafttech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

List CustomResourceDefinitions

list_crds

List all CRDs with their API group, kind, scope, served and stored versions, age, and owner hint. Optionally fetch instance counts per CRD for deeper insight.

Instructions

Inventory every CRD with group, kind, scope, served versions, stored version, age, and an owner hint (Helm release / OLM CSV / known operator). Optional count_instances includes per-CRD instance counts (slower).

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_crds"
  }
}

Input Schema

NameRequiredDescriptionDefault
groupNoOptional API group filter (e.g. `argoproj.io`)
count_instancesNoInclude per-CRD instance counts (slower)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Discloses that it retrieves all CRDs with detailed fields and notes that including instance counts is slower. Since no annotations are provided, the description carries the full burden for behavioral transparency, which it meets adequately.

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?

Two sentences concisely convey the output and the optional parameter with its trade-off. No redundant information, and it is front-loaded with the main purpose.

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 listing tool with two parameters and no output schema, the description covers the return fields and the optional parameter's behavior adequately. It is complete enough for an agent to decide whether to use it.

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?

Adds meaning beyond the schema by describing what 'count_instances' does and that it is slower, which aids decision-making. The schema already covers both parameters, so the description enhances rather than repeats.

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 it inventories every CRD with specific fields (group, kind, scope, versions, age, owner hint), distinguishing it from sibling tools like 'describe_crd' which focus on a single CRD. The verb 'inventory' is specific and matches the tool's action.

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?

Provides clear context about the optional 'count_instances' parameter and its performance impact. While it doesn't explicitly contrast with alternatives, the scope of listing all CRDs is well-defined, and the cost annotation guides usage.

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