Skip to main content
Glama
bezata

kObsidian MCP

Edit Canvas

canvas.edit

Add, connect, or remove nodes and edges on a canvas. Insert text or file nodes at coordinates, link nodes with directed edges, and delete nodes to remove all connections.

Instructions

Mutate a canvas: add a node, add an edge, or remove a node. The op field selects the mutation. add-node needs nodeType (text for inline markdown or file for an embedded note), content, x, y (plus optional width/height). add-edge needs fromNode and toNode ids (plus optional label). remove-node needs nodeId — removing a node also removes every edge incident to it (destructive). Returns a standard mutation envelope.

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

Examples:

Example 1 — Add a text node to a canvas:

{
  "op": "add-node",
  "filePath": "Boards/map.canvas",
  "nodeType": "text",
  "content": "Research question",
  "x": 0,
  "y": 0,
  "width": 280,
  "height": 80
}

Example 2 — Connect two existing nodes with a labelled edge:

{
  "op": "add-edge",
  "filePath": "Boards/map.canvas",
  "fromNode": "n1",
  "toNode": "n2",
  "label": "depends on"
}

Example 3 — Remove a node and all its edges:

{
  "op": "remove-node",
  "filePath": "Boards/map.canvas",
  "nodeId": "n3"
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

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

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

The description discloses that removing a node also removes incident edges (destructive behavior), which is not captured by annotations. It also implies mutation operations. However, the annotation destructiveHint=false conflicts with the description's statement about destructiveness.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with a summary, parameter breakdown, vault context, and three examples. It is slightly verbose but each sentence adds value. Front-loading the mutation types is helpful.

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 complexity of the tool (multiple operations, many parameters, destructive behavior, vault context), the description covers all essential aspects. Examples for each operation and mention of return envelope make it complete.

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?

Despite the input schema being empty (0 parameters), the description thoroughly explains all parameters for each operation, including types and optionality. Examples further clarify usage. This compensates for the missing 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 clearly states the tool mutates a canvas by adding a node, adding an edge, or removing a node. It provides specific verbs and resources, distinguishing the three operations.

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 provides clear context for when to use each operation, including required and optional parameters. However, it does not explicitly compare this tool to sibling tools like canvas.create or canvas.connections, which could help the agent choose between them.

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