Skip to main content
Glama
bezata

kObsidian MCP

by bezata
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

Parse Kanban Board

kanban.parse
Read-onlyIdempotent

Parse markdown Kanban boards into columns and cards with completion state, delivering full board content from obsidian-kanban format.

Instructions

Parse a markdown Kanban board file into its column/card structure. Use this when you need the full board content — each column's name and its cards with their completion state. Works with the obsidian-kanban plugin's markdown format. Read-only. For completion counts and ratios instead of the full card list, use kanban.stats.

Operates on the session-active vault (see vault.current — selectable via vault.select) unless an explicit vaultPath argument is passed, which always wins.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filePathYesPath of the Kanban board note (`.md`).
vaultPathNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
columnsYes
filePathYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Addedv0.3.5
  2. Removedv0.3.4
  3. Changed6 schema fields changedv0.1.2
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / description
      Added value: +"Arguments for `kanban.parse`."
    • addedInput schema / properties / filePath / description
      Added value: +"Path of the Kanban board note (`.md`)."
    • addedOutput schema / properties / columns
      Added value: +{
+  "items": {
+    "additionalProperties": {},
+    "properties": {
+      "cards": {
+        "items": {
+          "additionalProperties": {},
+          "properties": {
+            "completed": {
+              "type": "boolean"
+            },
+            "text": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "text",
+            "completed"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "name": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "name",
+      "cards"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • addedOutput schema / properties / filePath
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / required
      Added value: +[
+  "filePath",
+  "columns"
+]
  4. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the description's 'Read-only' adds no new safety info. However, it adds valuable behavioral context beyond annotations: compatibility with the obsidian-kanban plugin format and the session-active vault behavior with vaultPath override. This improves the agent's understanding of execution context.

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 tight and front-loaded. The first sentence states the core purpose; the next sentences provide usage guidance, an explicit alternative, and the vault behavior. Every sentence earns its place with no redundant or vague 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 output schema exists and annotations cover safety, the description is complete. It explains what the tool does, when to use it, which format is supported, and how vault selection works. No missing critical context for an agent 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 50%: filePath is documented in the schema, vaultPath is not. The description compensates for vaultPath by explaining it overrides the session-active vault, giving that parameter meaningful semantics beyond its bare type. It could be stronger with path format details, but the description adds real value.

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 uses a specific verb and resource: 'Parse a markdown Kanban board file into its column/card structure.' It clearly distinguishes itself from kanban.stats by explaining that this tool provides the full board content, not just counts.

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?

Explicitly states when to use the tool: 'Use this when you need the full board content.' It also names the alternative for different needs: 'For completion counts and ratios instead of the full card list, use kanban.stats.' This leaves no ambiguity about tool selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bezata/kObsidian'

If you have feedback or need assistance with the MCP directory API, please join our Discord server