Skip to main content
Glama
adalekin

weeek-mcp

by adalekin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

weeek_manage_board_columns

Create, rename, delete, or reorder board columns in Weeek to manage task workflow statuses. Read columns with weeek_list_board_columns.

Instructions

Create, rename, delete or reorder a board column (status). Use weeek_list_board_columns to read them.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoRequired for create and update.
actionYes
board_idNoRequired for create.
board_column_idNoRequired for everything but create.
upper_board_column_idNomove: the column to sit after; null moves it first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.2
    • addedInput schema / properties / upper_board_column_id / anyOf
      Added value: +[
+  {
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedInput schema / properties / upper_board_column_id / type
      Removed value: -[
-  "integer",
-  "null"
-]
  2. First observedv0.2.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description bears full behavioral burden. It doesn't disclose authorization requirements, whether delete is permanent, what happens to tasks in a deleted column, or whether reordering affects other boards. Only the basic CRUD verbs are stated.

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?

Two short sentences with zero waste. The main purpose is front-loaded and the guidance note follows immediately.

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 mutation tool with no annotations and no output schema, the description is under-specified. It doesn't cover permissions, side effects (especially for delete/move), error behaviors, or what the response contains. The schema covers parameters, but behavioral context is largely missing.

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 80%, which is high, so the schema already documents most parameters (name, board_id, board_column_id, upper_board_column_id). The description only implies the action modes but adds no syntax or edge-case detail beyond what the schema provides, setting the baseline at 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 clearly states a specific verb set (create, rename, delete, reorder) and the resource (board column / status). It names a sibling read tool, weeek_list_board_columns, creating some differentiation, though it doesn't distinguish itself from other manage-style tools as sharply as possible.

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?

The second sentence explicitly points to weeek_list_board_columns for reading, which is a clear alternative. However, it doesn't state when to prefer this tool's create vs update vs delete vs move actions beyond the schema enum, leaving some usage inference to the agent.

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