Skip to main content
Glama
KpihX

tick-mcp

by KpihX
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

manage_columns

Create, update, or delete kanban columns in batch for a project. Manage column names and order efficiently.

Instructions

Create, update, or delete kanban columns in batch.

[Category: Kanban Columns]  [Auth: V2]
[Related: list_columns, create_task, update_task]
[Workflow: Create kanban project → manage_columns → create_task with column_id]

Args:
    project_id: The project these columns belong to.
    add: New columns: [{"name": "To Do", "sortOrder": 0}, {"name": "In Progress", "sortOrder": 1}].
        projectId is auto-filled.
    update: Column updates: [{"id": "...", "name": "New Name"}].
    delete: Column IDs to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYes
addNo
updateNo
deleteNo

Tool Definition Quality

A4.2/5.0
Behavior3/5

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

With no annotations, the description carries full burden. It mentions auto-filling projectId but lacks details on auth, rate limits, or failure behavior. Adequate but not thorough.

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?

Well-structured with sections, concise (few lines), and every sentence provides value. Efficient use of space.

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

Completeness4/5

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

Covers main aspects: batch operation, parameter formats, related tools, and workflow. Lacks output or error handling details, but acceptable for a mutation tool without output schema.

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?

Schema coverage is 0%, but description adds examples and auto-fill note for 'add', and clarifies expected structures for update and delete. Significantly aids understanding beyond schema.

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 clearly states it can create, update, or delete kanban columns in batch, with specific verb and resource. It distinguishes from siblings like list_columns and create_task.

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

Usage Guidelines4/5

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

Provides a workflow hint and related tools, giving context for when to use. Lacks explicit 'when not to use' but offers sufficient guidance.

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

Install Server

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/KpihX/tick-mcp'

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