Skip to main content
Glama
Sign In
Obsidian MCP Wrapper

Obsidian MCP Wrapper

by UwUGreed
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

strategy_search

Search an Obsidian vault to retrieve relevant notes and knowledge by providing a query, with optional limits on token usage and result count.

Instructions

strategy_search

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

Input Schema

NameRequiredDescriptionDefault
queryYes
max_tokensNo
max_resultsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.1/5.0
Behavior1/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 disclosing side effects, permissions, rate limits, or return behavior. The description simply restates the name and reveals nothing beyond the fact that some search operation may occur.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very short but this is under-specification, not conciseness. It contains a single word and earns no place because it supplies zero informative content.

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

Completeness1/5

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

With 3 parameters, no output schema, and 12 sibling tools providing potential alternatives, this description is completely inadequate. An agent cannot know what the tool does, when to invoke it, or how to configure it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description adds no meaning to the parameters (query, max_tokens, max_results). The agent receives no hints about query syntax, result limits, or token usage.

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

Purpose1/5

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

Tautological: description restates name/title.

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

Usage Guidelines1/5

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

The description offers no guidance on when to use this tool or when to prefer an alternative. There are no usage contexts, exclusions, or comparisons to sibling tools.

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