@vibemap.ai/mcp-server

vibemap_update_kanban_status

Idempotent

Advance or update the kanban status of features, user stories, or acceptance criteria by validating allowed state transitions.

Instructions

[DEPRECATED — use the typed transition tools (claim, report_progress, submit_for_review, resolve_review, block, unblock) instead. This tool will be removed in a future release.] Atomically advance or update the kanban status of a feature, user story, or acceptance criterion. Validates allowed state transitions and prevents invalid moves. Call this when you start or finish implementing something.

Feature stages: draft → open → in_progress → completed Story stages: draft → has_criteria → open → in_progress → completed Criterion stages: draft → pending → passed | failed

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "entityType": "<entityType>",
      "entityId": "<entityId>",
      "newStatus": "<newStatus>"
    },
    "name": "vibemap_update_kanban_status"
  }
}

Input Schema

Name	Required	Description
`notes`	No	Optional context about why this transition was made
`entityId`	Yes	ID of the feature, story, or criterion
`newStatus`	Yes	Target kanban status
`entityType`	Yes	Type of item to update

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.5.2Jul 26, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations indicate idempotentHint=true and destructiveHint=false. The description adds behavioral context beyond annotations: it validates allowed state transitions, prevents invalid moves, and lists valid stage sequences for each entity type. No contradictions detected.

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

Conciseness4/5

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

The description is concise (two sentences plus stage lists) and front-loaded with the deprecation warning. Every sentence serves a purpose: deprecation notice, atomic action, validation, usage context, and stage diagrams. Minor room for even tighter phrasing.

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

Completeness5/5

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

Given the tool's deprecation status and the absence of an output schema, the description covers all necessary context: why to avoid it, what it does, valid transitions, and entity types. It is complete for an agent to understand when and how to invoke it correctly.

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 100% (4 parameters documented). The description adds semantic value by enumerating allowed statuses per entity type (draft→open→in_progress→completed, etc.), which helps understand the newStatus parameter beyond its enum definition.

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 the tool's purpose: it atomically advances/updates the kanban status of features, stories, or criteria. It also distinguishes itself from sibling typed transition tools by explicitly deprecating itself and recommending alternatives.

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

Usage Guidelines5/5

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

The description provides explicit when-to-use guidance: 'Call this when you start or finish implementing something.' It also clearly states that the tool is deprecated and that typed transition tools should be used instead, offering strong usage boundaries.

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

Deploy Server