Skip to main content
Glama
Sign In
MCP cldkctl Server

MCP cldkctl Server

by raffelprama
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

cldkctl_k8s_deployments

Deploy and manage Kubernetes applications on Cloudeka by specifying project ID and namespace for container orchestration.

Instructions

Call the cldkctl_k8s_deployments endpoint

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project_id": "<project_id>",
      "namespace": "<namespace>"
    },
    "name": "cldkctl_k8s_deployments"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesProject ID
namespaceYesNamespace

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

D1.4/5.0
Behavior1/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It fails to indicate whether this is a read, write, or destructive operation, what permissions are required, or any side effects. The vague 'call the endpoint' adds no useful context beyond the name.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

While concise, the single sentence 'Call the cldkctl_k8s_deployments endpoint' is under-specified and fails to convey essential information. Conciseness should not come at the cost of clarity; this description wastes its opportunity to inform the agent effectively.

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

Completeness1/5

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

The description is completely inadequate for a tool with no annotations and no output schema. It lacks purpose, usage guidelines, behavioral details, and any context about returns or errors, leaving the agent unable to understand or invoke the tool correctly in a complex Kubernetes environment.

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%, with clear parameter documentation for 'project_id' and 'namespace'. The description adds no additional meaning beyond the schema, such as format examples or constraints, but the schema adequately covers the basics, meeting the baseline for high coverage.

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

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Call the cldkctl_k8s_deployments endpoint' is a tautology that merely restates the tool name without explaining what it actually does. It lacks a specific verb (e.g., list, create, update) and resource (e.g., Kubernetes deployments), failing to distinguish it from sibling tools like 'cldkctl_get_deployment' or 'cldkctl_create_deployment'.

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

Usage Guidelines1/5

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

No guidance is provided on when to use this tool versus alternatives. Given the many sibling tools related to deployments (e.g., create, delete, edit, get), the description offers no context, prerequisites, or exclusions, leaving the agent with no basis for selection.

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