Skip to main content
Glama

kaiten_create_custom_property

Create custom properties for Kaiten cards by specifying a name and type, with options for validation, colors, multi-select, and display settings.

Instructions

Create a company custom property.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNoType-specific data (e.g. restrictions {min, max} for number, {minLength, maxLength} for string; vote scale config for vote types)
nameYesProperty name (1-255 chars)
typeYesProperty type
colorNoColor index
colorfulNoEnable colors for select values
multilineNoMultiline text field (for string type)
values_typeNoValues type (required for collective_score type)
multi_selectNoEnable multi-select (for select type)
vote_variantNoVote variant (required for vote/collective_vote types)
show_on_facadeNoShow on card facade
values_creatable_by_usersNoAllow regular users to create new select values (for select type)
Install Server

TDQS

B3.2/5.0
Behavior2/5

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

The description discloses only that the tool creates a custom property, with no additional behavioral context such as permission requirements, whether the operation is destructive, how type-specific data affects the created property, or what the response will be. Since no annotations are provided, the description carries the full burden but does not meaningfully go beyond the tool name.

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

Conciseness5/5

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

The description is a single, compact sentence with no filler or repeated schema content. It is front-loaded with the key action and resource, making it easy to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a create operation with 11 parameters, many type-specific conditional requirements, and no output schema, a one-sentence description is insufficient. The schema helps, but the description does not mention the need to pass type-specific configuration via the 'data' object or any expected behavior after creation, leaving the agent without enough high-level 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?

The input schema has 100% parameter description coverage, so the baseline is 3. The description itself adds no parameter-level insight, but the schema already documents all parameters clearly, including type-specific data and conditional fields.

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

Purpose5/5

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

The description states a clear, specific action ('Create') and a specific resource ('company custom property'), which distinguishes it from sibling tools like list/get/update/delete custom property and from other create_* tools. Even though it is short, the verb and resource are unambiguous.

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?

The description provides no guidance on when to use this tool versus alternatives such as kaiten_update_custom_property or kaiten_create_select_value. No exclusions, prerequisites, or context are given, so the agent must infer usage entirely from the name and schema.

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

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ViktorOgnev/kaiten-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server