Planka MCP Server

bootstrap

Retrieve current user, projects, boards, and notifications from Planka. Get all essential app data in a single request.

Instructions

Get Planka application bootstrap data including current user, projects, boards, and notifications.

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": {
      "action": "<action>"
    },
    "name": "bootstrap"
  }
}

Input Schema

Name	Required	Description	Default
`action`	Yes	Action: 'get' - Retrieve bootstrap data

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.4Aug 6, 2026

TDQS

B3.4/5.0

Behavior2/5

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

With no annotations, the description carries the full transparency burden. It uses the verb 'Get' suggesting a read operation, but does not disclose authentication needs, side effects, rate limits, or any safety related behavior beyond the implicit read.

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 a single, front-loaded sentence that states the action and resource without redundancy. Every word contributes meaning, making it highly concise and structured.

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?

Given the absence of an output schema, the description provides useful context by enumerating the key return components (user, projects, boards, notifications). It doesn't exhaustively list all possible fields, but is sufficient for a simple bootstrap tool with one parameter.

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 fully covers the only parameter 'action' with an enum and description, achieving 100% coverage. The description adds no parameter-specific details, so the baseline score of 3 is appropriate.

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 retrieves Planka bootstrap data, listing the included resources (current user, projects, boards, notifications). This distinguishes it from sibling tools that each manage a single resource, making the purpose unmistakable.

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?

No guidance is provided on when to choose this tool over siblings like 'projects' or 'boards'. The description implies it fetches a consolidated snapshot, but doesn't explicitly say to use it for app initialization or instead of multiple individual calls.

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

Deploy Server