Skip to main content
Glama
Sign In
Obsidian MCP Server

Obsidian MCP Server

by cupkappu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

search_simple

Search your Obsidian vault for specific text. Returns matching notes with context around each match.

Instructions

Perform a simple text search across the vault

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": {
      "query": "<query>"
    },
    "name": "search_simple"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesSearch query
contextLengthNoAmount of context to return around matches

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations, the description must carry the full behavioral burden. It merely restates the action without disclosing return format, read-only nature, search semantics (e.g., case sensitivity, regex), or side effects. This adds minimal value beyond the tool name.

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, front-loaded sentence with no wasted words. It is concise and well-structured for a tool of this simplicity.

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?

With no output schema and no annotations, the description does not explain what a search result looks like or how 'contextLength' affects output. For a standalone tool, this is a significant gap in completeness.

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 provides 100% coverage with descriptions for both 'query' and 'contextLength'. The description adds no additional parameter semantics, so the baseline score of 3 applies due to high schema coverage.

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 performs a text search across the vault, using a specific verb and resource. This distinguishes it from sibling tools, which are all file/command operations, making the purpose unambiguous.

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 phrase 'simple text search' implies usage for basic search within the vault, but there is no explicit when-to-use guidance or mention of alternatives. Since no other search tool exists among siblings, the guidance is implicitly clear but not articulated.

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

Deploy Server

Other Tools