Skip to main content
Glama
jagoff

obsidian-mcp-complete

by jagoff
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

obsidian_open_uri

Read-only

Construct an obsidian://open URI for a note using its vault-relative path, enabling direct links to open notes.

Instructions

Build an obsidian://open URI for a note. This does not execute OS commands.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
vaultNoOptional configured vault name. Defaults to the server default vault.
pathYesVault-relative path. Absolute paths and traversal are rejected.

Implementation Reference

  • src/tools.ts:1295-1305 (handler)
    Handler for obsidian_open_uri tool: builds an obsidian://open URI string for a given vault note path. Does not execute the URI (it just constructs it).
    tool(
  "obsidian_open_uri",
  "Build an obsidian://open URI for a note. This does not execute OS commands.",
  { vault: vaultArg, path: pathArg },
  (args) => {
    const vault = vaults.getVault(args.vault);
    const file = encodeURIComponent(vaults.notePath(args.path));
    return { uri: `obsidian://open?vault=${encodeURIComponent(vault.name)}&file=${file}` };
  },
  { readOnlyHint: true },
);

Tool Definition Quality

A4/5.0
Behavior4/5

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

Annotations already indicate read-only and non-destructive behavior. The description adds that it 'does not execute OS commands', which is a crucial behavioral trait beyond what annotations provide, aligning with the readOnlyHint.

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 two succinct sentences with no wasted words. It is front-loaded with the action immediately, and every sentence adds value.

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?

For a simple tool that builds a URI, the description is adequate. It does not explain the return value, but given the tool's purpose, it is likely clear. No output schema is provided, but the context is sufficient for selection and invocation.

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?

Input schema has 100% coverage with descriptions for both parameters (vault and path). The description adds no additional meaning beyond what the schema already provides, so baseline score of 3 applies.

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 'Build an obsidian://open URI for a note', which clearly identifies the action (build) and resource (URI for a note). It explicitly distinguishes itself from actual opening of the URI, differentiating it from sibling tools like 'obsidian_open_in_ui'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description notes that it 'does not execute OS commands', implying it should be used when only the URI is needed, but it does not explicitly state when to use this tool versus alternatives (e.g., when to use obsidian_open_in_ui instead).

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/jagoff/obsidian-mcp'

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