Skip to main content
Glama

kelpo_create_project

Create a conversation (one video) in a workspace: body client_id. Returns its id and project_version (version 0). Arguments: {"body": {"client_id": ""}}

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

Input Schema

NameRequiredDescriptionDefault
bodyNo

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

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnly=false, destructive=false, idempotent=false, so the safety profile is covered. The description adds genuinely useful return info (id and project_version 0) absent from any output schema, but says nothing about the non-idempotent duplicate-creation risk or what happens when client_id is omitted.

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

Conciseness3/5

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

The core sentence is front-loaded and useful, but the fragment 'body client_id' and the trailing JSON argument example duplicate what the schema already shows, adding noise for a single optional parameter.

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 one-parameter tool with annotations, the description covers what it creates and that version 0 is returned. The remaining gaps — optionality of client_id and its source, plus non-idempotency implications — are moderate but real for a creation tool with no output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the burden, but it merely restates the schema shape ('{"body": {"client_id": ...}}') without explaining what a client id is, where to get one, or that it is optional (required=[]). Repetition of structure is not added semantics.

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 names a specific verb and resource and goes further by defining the domain object: a 'conversation (one video) in a workspace'. That disambiguates it from kelpo_create_client and kelpo_get_project. It stops short of explicitly naming the nearest sibling, so 4 rather than 5.

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

Usage Guidelines2/5

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

There is no statement of when to call this versus alternatives (kelpo_get_project, kelpo_create_client) and no prerequisites, even though 'in a workspace' implies a client/workspace must exist first. Usage is only inferable from the verb.

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