Skip to main content
Glama
Sign In
weeek-mcp

weeek-mcp

by MaxViksna
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Create board column

weeek_create_board_column

Creates a new column on a specified board. Requires a column name and board ID.

Instructions

POST /tm/board-columns. Create board column. Tags: BoardColumn. Body: application/json.

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

Input Schema

NameRequiredDescriptionDefault
bodyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It indicates a POST (create) operation but does not mention side effects, authentication needs, idempotency, or any constraints beyond what is implied by the operation. The minimal description adds little beyond the name and schema.

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 description is very concise (13 words) and front-loaded with the HTTP method, but it lacks structure. It is not verbose, but the extreme brevity sacrifices clarity and completeness.

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

Completeness1/5

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

Given the lack of annotations, output schema, and parameter descriptions, the description is severely incomplete. It does not explain what a board column is, how to use it within the broader API, or what the response looks like. The agent is left with insufficient context to select or invoke the tool correctly compared to many siblings.

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

Parameters1/5

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

Schema description coverage is 0%, and the description adds no explanation for the 'name' and 'boardId' parameters. It only says 'Body: application/json', which is already implied by the schema. The agent receives no semantic help for constructing the request body.

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 'Create board column' and includes the HTTP method and endpoint. It's specific enough to differentiate from siblings like 'weeek_update_board_column' but does not explicitly contrast with them.

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. It does not mention prerequisites (e.g., requiring an existing board) or exclude any use cases. Siblings like 'weeek_create_board' and 'weeek_update_board_column' remain undifferentiated.

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