Skip to main content
Glama
Sign In
KubeCraft MCP Server

KubeCraft MCP Server

by cloudcrafttech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

List Resource Quotas

list_resource_quotas

List ResourceQuotas with used versus hard limits and LimitRanges with min/max/default constraints for a Kubernetes namespace.

Instructions

List ResourceQuotas showing used vs hard limits, and LimitRanges showing min/max/default resource constraints per namespace.

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

Input Schema

NameRequiredDescriptionDefault
namespaceNoKubernetes namespace (default: 'default')default

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided. The description does not disclose behavioral traits such as permissions needed, whether it lists all namespaces if parameter omitted, or pagination behavior. It only states what it does, not how it behaves.

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?

The description is a single concise sentence of about 20 words, front-loaded with the key action. It is efficient but could be slightly more detailed.

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?

Given the simplicity of the tool (one parameter, no output schema), the description provides adequate information about what it lists. However, it lacks details on output format or behavior for missing namespace, leaving some gaps for the agent.

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 documentation covers the namespace parameter fully (100% coverage). The description does not add additional meaning beyond the schema, so baseline 3 is appropriate.

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 ResourceQuotas and LimitRanges, specifying the information shown (used vs hard limits, min/max/default constraints). It distinguishes from many sibling list tools focused on other resources.

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?

No guidance on when to use this tool versus alternatives. There are many list_ tools, but the description does not provide context on when to choose this over others.

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