Obsidian Server MCP

Overview Schema Source Related Servers Discussions Admin

search_query

Read-onlyIdempotent

Query Markdown notes in an Obsidian vault using JsonLogic filters over path, content, tags, frontmatter, and file stats; optional scope limits scans while path and glob conditions filter results.

Instructions

Query Markdown with JsonLogic over path, content, tags, frontmatter and stat. Returns truthy values. Only scope limits the scan; query path/glob conditions only filter results. Overflow errors, never truncation. No link graph.

Input Schema

Name	Required	Description
`query`	Yes
`scope`	No	Optional scan scope; omit for a recursive whole-Vault scan. directory "" is root; recursive=false scans only direct child files.
`maxFiles`	No	Optional scanned-file cap; omit for defaults.
`maxEntries`	No	Optional scanned-entry cap; omit for defaults.
`maxResults`	No	Optional match cap, not truncation; omit for defaults.
`maxFileBytes`	No	Optional per-file byte cap; omit for defaults.
`maxTotalBytes`	No	Optional scanned-byte cap, not response size; omit for defaults.

Output Schema

Name	Required	Description	Default
`results`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.2.0Oct 24, 2026

addedOutput schema / properties / results / items / properties / versionGuard

Added value: +{
+  "maxLength": 16,
+  "minLength": 16,
+  "pattern": "^[0-9a-f]{16}$",
+  "type": "string"
+}

changedOutput schema / properties / results / items / required

Previous value: -[
-  "filename",
-  "version",
-  "result"
-]New value: +[
+  "filename",
+  "version",
+  "versionGuard",
+  "result"
+]

Changed1 schema field changedOct 3, 2026

addedInput schema / properties / scope

Added value: +{
+  "additionalProperties": false,
+  "description": "Optional scan scope; omit for a recursive whole-Vault scan. directory \"\" is root; recursive=false scans only direct child files.",
+  "properties": {
+    "directory": {
+      "type": "string"
+    },
+    "recursive": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "directory",
+    "recursive"
+  ],
+  "type": "object"
+}

First observedv0.1.0Oct 3, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the description earns credit for adding real behavior: truthy-value returns, overflow-errors-instead-of-truncation, and the scan-vs-filter distinction. The explicit 'never truncation' guarantee is exactly the kind of failure-mode disclosure an agent needs before setting caps.

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?

Four short sentences, each carrying a distinct fact (fields, return semantics, scan-vs-filter, overflow behavior), with the core purpose front-loaded. No filler and no repetition of schema content.

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

Completeness3/5

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

With an output schema present, return values need not be described, and the scan/error semantics are well covered for a 7-parameter tool. The gap is the query DSL itself: no mention of which JsonLogic operators or field names are valid, which is the hardest part of invoking this tool correctly.

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?

Schema coverage is 86%, so the baseline is 3; the description pushes above it by explaining that scope is the sole scan driver and that result caps are not truncation, which clarifies the intent behind maxResults and maxFiles. It still says nothing about the JsonLogic object shape required by the sole required parameter.

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?

States a specific verb and resource ('Query Markdown') plus the mechanism and queryable fields (path, content, tags, frontmatter, stat), which lets an agent tell it apart from vault_list, tag_list and reference_query. The trailing 'No link graph' explicitly carves out the graph-query sibling.

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?

Provides one important usage rule -- that only scope limits the scan while path/glob conditions merely filter results -- which shapes how an agent should build a query. However, it never names an alternative tool or states when to prefer vault_list/tag_list over this one; the 'No link graph' clause is the only implied exclusion.

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

Deploy Server