obsidian-modified-mcp-server

Overview Schema Source Related Servers Discussions Admin

open_file

Opens a specified file in Obsidian using its path relative to the vault root. Accepts an optional vault ID to target a specific vault.

Instructions

Open a file in Obsidian.

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": {
      "filepath": "<filepath>"
    },
    "name": "open_file"
  }
}

Input Schema

Name	Required	Description	Default
`vaultId`	No	Optional vault ID (defaults to configured default vault).
`filepath`	Yes	Path to the file to open (relative to vault root).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.6.0Jul 31, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does not state whether opening a file has side effects (e.g., changing the active pane), requires specific permissions, or what the return behavior is. This is a significant transparency gap.

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 sentence with no wasted words. It is maximally concise and avoids redundancy, earning a perfect score for structure.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simple nature of the tool, the description still incomplete. It lacks critical context such as what 'open' implies versus 'read', return values, error handling, and how it relates to sibling tools. Without annotations or an output schema, this minimal description is insufficient for an agent to use the tool correctly.

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 provides 100% description coverage for both parameters, so the baseline is 3. The description itself adds no additional meaning beyond what the schema already defines, but it does not need to compensate for any gaps.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Open') and the resource ('a file in Obsidian'), making it specific and unambiguous. However, it does not explicitly differentiate from sibling tools like get_file_contents, which could lead to confusion about whether 'open' means read or open in the UI.

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?

The description provides no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. It simply states the action without contextual direction.

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