Skip to main content
Glama
olgasafonova

productplan-mcp-server

by olgasafonova
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Local

manage_lane

Destructive

Create, update, or delete lanes on a roadmap to organize bars by category. Add, rename, reposition, or remove lanes to structure your roadmap's workflow.

Instructions

Create, update, or delete a lane on a roadmap.

USE WHEN: "Add Backend lane", "Rename Mobile lane", "Move lane to the top", "Delete lane" Actions: create (name; optional description, position), update (lane_id plus any of name, description, position), delete (lane_id) Returns the created/updated lane object, or confirmation on delete. FAILS WHEN: create without name, update/delete without lane_id (get IDs from get_roadmap_lanes), color passed (lanes have no settable color in the API). WARNING: delete removes the lane and unassigns all bars in it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoLane name
colorNoDEPRECATED and rejected: lanes have no color field in the ProductPlan API, so it was never applied
actionYescreate, update, or delete
lane_idNoLane ID (for update/delete)
positionNoPosition of the lane in the roadmap
roadmap_idYesRoadmap ID
descriptionNoWhat the lane represents

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv6.0.0
    • changedInput schema / properties / color / description
      Previous value: -"Hex color (#FF5733)"New value: +"DEPRECATED and rejected: lanes have no color field in the ProductPlan API, so it was never applied"
    • removedInput schema / properties / color / examples
      Removed value: -[
-  "#FF5733",
-  "#4CAF50"
-]
    • removedInput schema / properties / color / pattern
      Removed value: -"^#[0-9A-Fa-f]{6}$"
    • addedInput schema / properties / description
      Added value: +{
+  "description": "What the lane represents",
+  "type": "string"
+}
    • addedInput schema / properties / position
      Added value: +{
+  "description": "Position of the lane in the roadmap",
+  "examples": [
+    1
+  ],
+  "type": "integer"
+}
  2. First observedv5.0.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already indicate destructive behavior, but the description adds valuable specifics: deletion removes the lane and unassigns all bars in it, update requires a lane_id, and color is rejected. It also states what the tool returns per action, which is especially useful since there is no output schema.

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 well-structured with clear sections: summary, USE WHEN, Actions, Returns, FAILS WHEN, and WARNING. Every section adds operational value, and there is no filler or repetition beyond what is necessary.

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?

For a 7-parameter CRUD tool with three action modes and no output schema, the description is operationally complete. It covers when to use it, per-action parameter requirements, return behavior, failure conditions, and the destructive consequence of deletion.

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 description coverage is 100%, so the schema already documents each parameter. The description adds meaningful conditional semantics beyond that: create requires name, update requires lane_id plus any mutable fields, delete requires lane_id, and color is always invalid.

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 opens with a specific verb phrase, 'Create, update, or delete a lane on a roadmap,' which names both the action set and the exact resource. This clearly differentiates it from sibling tools like manage_bar or manage_milestone.

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 'USE WHEN' section provides concrete natural-language triggers such as 'Add Backend lane' and 'Delete lane,' making it easy for an agent to know when to select this tool. It also points to get_roadmap_lanes for obtaining IDs, though it does not explicitly discuss when-not-to-use or all alternative tools.

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