Skip to main content
Glama

kelpo_create_client

Create a workspace for a person or brand (name). Its id is the client_id of kelpo_create_project, kelpo_actor_catalog and kelpo_outfit_catalog. Arguments: {"body": {"name": ""}}

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": {
      "body": "<body>"
    },
    "name": "kelpo_create_client"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / body / type
      Added value: +"object"
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent, closed-world mutation, so the safety profile is covered. The description usefully adds that the creation yields an id consumed downstream, confirming a persistent entity is produced. It does not warn about duplicate creation risk (despite idempotentHint=false) or what a failed/duplicate call returns.

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?

Two short sentences: purpose first, then the downstream id relationship, then the argument shape. Front-loaded and efficient. Minor redundancy in restating the body/name shape already in the schema, but it does aid quick invocation.

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?

For a creation tool with one required nested object, annotations and no output schema, the description covers purpose, argument for name, and downstream id linkage. It falls short on the undocumented 'notes' parameter and on non-idempotency/duplicate-handling behavior, which matter for a create call.

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 0%, so the description has to compensate. It does explain body.name ('name of the person or brand') via the JSON argument example, but the optional 'notes' field (max 1000 chars) is never mentioned in the description, leaving it discoverable only from the raw schema. Partially compensating, hence a 3.

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

Purpose4/5

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

The description gives a specific verb + resource: 'Create a workspace for a person or brand'. It clearly distinguishes the tool from the read-side sibling kelpo_list_clients by describing creation. The slight terminology drift between 'client' in the tool name and 'workspace' in the description is resolved by the mention of client_id.

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

Usage Guidelines3/5

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

Usage is implied through dependency context: the returned id is the client_id needed by kelpo_create_project, kelpo_actor_catalog and kelpo_outfit_catalog, which tells the agent to call this first. However, there is no explicit when-to-use or when-not guidance, no mention of checking duplicates via kelpo_list_clients first, and no prerequisites stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources