Skip to main content
Glama
bezata

kObsidian MCP

by bezata
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

Create Canvas

canvas.create

Create a new Obsidian canvas (.canvas) file at a given path, with optional overwrite. Use for spatial whiteboards with nodes and edges.

Instructions

Create a new empty Obsidian canvas (.canvas) file at the given path. Fails if the path already exists unless overwrite: true is passed. Canvas files are JSON documents that Obsidian renders as an infinite spatial whiteboard of nodes and edges. Use canvas.edit to add nodes/edges once the file exists.

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 for the new canvas (must end in `.canvas`).
overwriteNoWhen true, overwrite an existing canvas at the path. Defaults to false.
vaultPathNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetYesThe path or identifier the tool acted on.
changedYesTrue if the tool altered vault state on this call; false if it was a no-op.
summaryYesShort human-readable summary of what happened.

Schema Changelog

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

  1. Changed2 schema fields changedv0.3.5
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed7 schema fields changedv0.1.2
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / filePath / description
      Added value: +"Path for the new canvas (must end in `.canvas`)."
    • addedInput schema / properties / overwrite / description
      Added value: +"When true, overwrite an existing canvas at the path. Defaults to false."
    • addedOutput schema / description
      Added value: +"Standard mutation envelope. Individual tools may attach additional fields (e.g. `created`, `appended`, `before`/`after` counts) — those are documented in the tool description."
    • addedOutput schema / properties / changed / description
      Added value: +"True if the tool altered vault state on this call; false if it was a no-op."
    • addedOutput schema / properties / summary / description
      Added value: +"Short human-readable summary of what happened."
    • addedOutput schema / properties / target / description
      Added value: +"The path or identifier the tool acted on."
  3. First observedv0.1.0

TDQS

A4.1/5.0
Behavior1/5

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

The description is transparent about failure behavior and overwrite semantics, but annotations declare destructiveHint:false while the description states that overwrite:true overwrites an existing file. That is a contradiction on a safety-critical behavioral trait, so this dimension must be scored down despite the otherwise strong disclosure.

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 front-loaded with the core action, then adds only necessary details: failure behavior, file format relevance, next-step sibling, and vault targeting. Every sentence earns its place and there is no filler.

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 create operation with an output schema, the description covers the essential invocation context: target path, overwrite behavior, vault resolution, file type, and follow-up editing tool. An agent has enough information to call it correctly in most scenarios.

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?

The schema documents filePath and overwrite, but vaultPath has no schema description. The tool description compensates by explaining vaultPath precedence over the session-active vault, which is exactly the missing semantic context an agent needs. It also reinforces the overwrite behavior with the fail-if-exists default.

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 action ('Create'), a precise resource ('new empty Obsidian canvas (.canvas) file'), and path-based placement. It also distinguishes itself from the sibling canvas.edit by making clear that canvas.edit is for adding nodes/edges after the file exists.

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?

It explicitly says to use this tool first and then canvas.edit for nodes/edges, providing a clear workflow. It also explains the overwrite condition and the session-active vault resolution, including the vault.select/vault.current relationship, which helps an agent decide how to target the right vault.

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