Skip to main content
Glama
Sign In
Obsidian MCP Extended

Obsidian MCP Extended

by aleksakarac
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

parse_kanban_board_tool

Parse markdown Kanban boards to extract columns, cards with due dates, tags, and wikilinks, along with subtask structure and statistics.

Instructions

Parse a Kanban board file and extract its structure (filesystem-native, offline).

Parses markdown-based Kanban boards with the following structure:

  • Column Name (level 2 or 3 headings)

  • Card text with metadata

    • Nested subtask

Metadata formats:

  • Due dates: @{YYYY-MM-DD}

  • Tags: #tag (inline)

  • Wikilinks: [[note]]

Supports nested subtasks with indentation levels.

When to use:

  • Analyzing board structure

  • Extracting card data programmatically

  • Generating board reports

  • Understanding card relationships

Performance:

  • Boards with 100 cards: < 500ms

  • Boards with 1,000 cards: < 5 seconds

Returns: Board structure with columns, cards, subtasks, metadata, and statistics

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": {
      "file_path": "<file_path>"
    },
    "name": "parse_kanban_board_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_pathYesPath to Kanban board file (relative to vault)
vault_pathNoPath to vault (optional, uses OBSIDIAN_VAULT_PATH env if not provided)
ctxNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

A4/5.0
Behavior3/5

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

No annotations provided, so description carries burden. It discloses performance benchmarks and metadata formats but does not explicitly state safety aspects (e.g., read-only nature) or required permissions.

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?

Well-structured with clear sections: summary, format details, metadata, usage, performance, returns. Every sentence adds value without redundancy.

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?

Describes input, process, and return value (board structure with columns, cards, etc.). Lacks edge-case handling (e.g., malformed boards) but is adequate for a read-only parsing tool.

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?

Schema coverage is 67% (ctx param undocumented). Description adds examples for file_path and explains vault_path uses env var, but ignores ctx parameter entirely.

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?

Description explicitly states the tool parses a Kanban board file and extracts its structure, with specific details on supported markdown formats. It distinguishes from siblings like add_kanban_card_tool and get_kanban_statistics.

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?

Lists clear when-to-use scenarios such as analyzing board structure and extracting card data. However, it does not mention when not to use or compare to similar tools like get_kanban_statistics.

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