Skip to main content
Glama
Sign In
MCP cldkctl Server

MCP cldkctl Server

by raffelprama
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

cldkctl_project_r_quota_post

Set or update resource quotas for a specific project in Cloudeka's cloud management platform using the cldkctl CLI functionality.

Instructions

Call the cldkctl_project_r_quota_post 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>"
    },
    "name": "cldkctl_project_r_quota_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesProject ID

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 for behavioral disclosure but offers no information. It does not indicate whether this is a read or write operation, what effects it has (e.g., modifies quota), authentication needs, rate limits, or error conditions.

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 description is under-specified and fails to convey useful information. It consists of a single vague sentence that does not earn its place by adding value beyond the tool name.

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 given the context. With no annotations, no output schema, and a vague purpose, it fails to provide necessary information for a tool that likely involves project quota operations, leaving significant gaps in understanding its behavior and use.

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 schema description coverage is 100%, with the single parameter 'project_id' clearly documented in the schema. The description adds no additional meaning or context about the parameter, so it meets the baseline of 3 where the schema handles documentation adequately.

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_project_r_quota_post endpoint' is a tautology that merely restates the tool name in different words. It fails to specify what action the tool performs (e.g., create, update, retrieve quota) or what resource it affects, and does not differentiate it from sibling tools like 'cldkctl_project_r_quota_pre'.

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 does not mention prerequisites, context, or exclusions, leaving the agent with no indication of appropriate usage scenarios.

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