Skip to main content
Glama
Sign In
MCP cldkctl Server

MCP cldkctl Server

by raffelprama
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

cldkctl_registry_labels_update

Update labels for container registries in Cloudeka's cloud platform to organize and manage resources effectively.

Instructions

Call the cldkctl_registry_labels_update 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": {
      "organization_id": "<organization_id>",
      "user_id": "<user_id>",
      "project_id": "<project_id>",
      "registry_id": "<registry_id>",
      "labels_data": "<labels_data>"
    },
    "name": "cldkctl_registry_labels_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
organization_idYesOrganization ID
user_idYesUser ID
project_idYesProject ID
registry_idYesRegistry ID
labels_dataYesLabels data

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?

With no annotations provided, the description carries full burden but offers no behavioral information. It doesn't indicate if this is a read or write operation, what permissions are needed, whether it's destructive, or any side effects like rate limits or response format, making it completely opaque.

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 with a single sentence, it's under-specified and fails to convey useful information. The brevity doesn't serve clarity, as it lacks essential details about the tool's purpose and usage, making it inefficient rather than appropriately sized.

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?

For a tool with 5 parameters, no annotations, and no output schema, the description is severely incomplete. It doesn't explain the tool's function, behavior, or output, leaving critical gaps that hinder an agent's ability to use it correctly in context.

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%, so the schema fully documents all 5 parameters. The description adds no additional meaning beyond the schema, such as explaining the structure of 'labels_data' or relationships between IDs, meeting the baseline for high coverage without extra value.

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_registry_labels_update endpoint' is a tautology that merely restates the tool name without explaining what it does. It doesn't specify the action (e.g., update, modify, set) or the resource (registry labels) in meaningful terms, and fails to distinguish it from sibling tools like cldkctl_registry_labels_create or cldkctl_registry_labels_delete.

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. It doesn't mention prerequisites, context, or differences from related tools such as cldkctl_registry_labels_create or cldkctl_registry_labels_delete, leaving the agent with no usage instructions.

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