obsidian-modified-mcp-server

Overview Schema Source Related Servers Discussions Admin

find_similar_notes

Find semantically similar notes to a given note in an Obsidian vault. Specify the source note's path and an optional similarity threshold to control the results.

Instructions

Find notes semantically similar to a given note.

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": "find_similar_notes"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Maximum similar notes to return (default: 10).
`vaultId`	No	Optional vault ID (defaults to configured default vault).
`filepath`	Yes	Path to the source note (relative to vault root). Forward-slash or backslash separators both accepted.
`threshold`	No	Similarity threshold 0-1 (default: 0.5).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.6.0Jul 31, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the core action and does not explain how similarity is computed, return format, sorting, error handling, or that it is a read-only operation. The description lacks meaningful behavioral 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 a single sentence, directly states the action, and contains no fluff. Every word contributes to understanding the tool's purpose, making it efficiently sized.

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 absence of an output schema and annotations, the description is too brief. It does not clarify the return value, ranking behavior, default thresholds, or error cases. While parameters are well-documented, the overall context for the agent is incomplete.

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 input schema covers 100% of parameters with descriptions for filepath, limit, threshold, and vaultId. The description text adds no parameter-level meaning, so it does not go beyond what the schema already provides. Baseline 3 is appropriate.

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 ('Find') + resource ('notes') + qualifier ('semantically similar to a given note'). It clearly distinguishes from sibling tools like semantic_search by indicating the input is an existing note (filepath) rather than a free-text query.

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?

Usage context is implied: use when you have a note and want to find semantically related notes. However, there is no explicit when-to-use vs alternatives, nor exclusions or comparison to sibling tools like semantic_search or search.

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