productplan-mcp-server

Overview Schema Source Related Servers Discussions Admin

get_bar_connections

Read-only

Retrieve bar dependencies to see which items block or depend on a given bar. Use this to answer questions like 'What depends on this?' and understand roadmap impacts.

Instructions

Get bar dependencies (what blocks what).

USE WHEN: "What depends on this?", "Show dependencies" FAILS WHEN: bar_id not found. Returns empty list if bar has no connections.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`bar_id`	Yes	Bar ID

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes	The ProductPlan payload (object or array) returned by the API, passed through verbatim
`summary`	Yes	Human-readable summary of the result (e.g. "Found 3 roadmaps")

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv6.0.0Sep 25, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "data": {
+      "description": "The ProductPlan payload (object or array) returned by the API, passed through verbatim",
+      "type": "object"
+    },
+    "summary": {
+      "description": "Human-readable summary of the result (e.g. \"Found 3 roadmaps\")",
+      "type": "string"
+    }
+  },
+  "required": [
+    "summary",
+    "data"
+  ],
+  "type": "object"
+}

First observedv5.0.0Mar 9, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations declare readOnlyHint=true, indicating a safe read operation. The description adds that it returns an empty list when no connections exist and fails when bar_id is not found, which are useful behavioral details beyond the annotation. It does not contradict annotations and adds practical context for error handling.

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 extremely concise: a one-line purpose followed by USE WHEN and FAILS WHEN sections. Every word serves a purpose, and the key information is front-loaded. There is no fluff or redundancy, making it easy for an agent to parse quickly.

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?

For a simple tool with a single parameter and an output schema present, the description covers the essential points: what it does, when to use it, and failure behavior. It does not explain the exact structure of the returned dependencies, but since an output schema exists, that is not required. It is sufficiently complete for correct invocation.

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?

The schema already documents bar_id with description 'Bar ID' and 100% coverage, so the baseline is 3. The description does not add any further detail about the parameter's format or meaning, but it doesn't need to since the schema is sufficient. No extra value provided beyond the 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 states a specific verb and resource: 'Get bar dependencies (what blocks what).' It clearly distinguishes the tool from siblings like get_bar (which fetches a bar), get_bar_children (which gets children), and get_bar_links (which gets links), making its purpose unambiguous.

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 description includes 'USE WHEN' cues with example user intents ('What depends on this?', 'Show dependencies'), providing clear context for when to invoke it. It also notes failure behavior (bar_id not found) and empty-list return, which helps agents decide if this is the right call. It does not explicitly list alternative tools to avoid, but the usage cues are adequate.

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

Deploy Server