Skip to main content
Glama
Sign In
MCP cldkctl Server

MCP cldkctl Server

by raffelprama
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

cldkctl_org_members

Manage organization members in Cloudeka's cloud platform by listing, adding, or removing users through the cldkctl CLI interface.

Instructions

Call the cldkctl_org_members endpoint

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": "cldkctl_org_members"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

D1.8/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. However, it only states the endpoint call without describing what the tool does (e.g., read vs. write operations, permissions needed, side effects, or response format). This is inadequate for a tool with potential organizational impact.

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?

The description is a single sentence but is under-specified, not concise. It wastes space by merely restating the tool name without adding value. Conciseness should not come at the cost of clarity, so this scores low.

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?

Given the lack of annotations, no output schema, and a vague description, the tool is incomplete. The description fails to explain what the tool does, its behavior, or when to use it, making it inadequate for an agent to invoke correctly in a context with many sibling tools.

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?

The input schema has 0 parameters with 100% coverage, meaning no parameters are documented in the schema. The description does not add parameter details, but since there are no parameters, this is acceptable. The baseline for 0 parameters is 4, as no compensation is needed.

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

Purpose2/5

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

The description 'Call the cldkctl_org_members endpoint' is tautological—it restates the tool name without explaining what it does. While the name suggests it relates to organization members, the description fails to specify the action (e.g., list, add, edit) or resource scope, making the purpose vague. It does not differentiate from sibling tools like 'cldkctl_org_member_add' or 'cldkctl_org_member_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. The description lacks context, prerequisites, or exclusions, and it does not reference sibling tools for comparison. This leaves the agent with no usage direction.

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