Skip to main content
Glama
bezata

kObsidian MCP

by bezata

Query Wiki

wiki.query
Read-onlyIdempotent

Rank wiki pages by relevance to your query, weighing filename, aliases, tags, summary, and body. Returns top matches with scores and hit fields to drill into strongest candidates.

Instructions

Rank wiki pages by relevance to a free-text topic, scanning Sources/Concepts/Entities pages. Hits are weighted in this order: filename match > frontmatter aliases > frontmatter tags > frontmatter summary > body. Returns up to limit pages (default 10, max 50) as {path, type, score, hitFields} so the agent can drill into the strongest candidates with notes.read. Read-only; never writes. Use this for 'what does the wiki know about X?' lookups; use wiki.lint instead for whole-vault health audits, and notes.search for raw full-text search outside the wiki layout.

Operates on the session-active vault (see vault.current — selectable via vault.select) unless an explicit vaultPath argument is passed, which always wins.

Examples:

Example 1 — Top 10 pages relevant to 'memex vs hypertext'.:

{
  "topic": "memex vs hypertext"
}

Example 2 — Top 25 pages on a narrow topic, custom wiki dir.:

{
  "topic": "circuit breaker pattern",
  "limit": 25,
  "wikiRoot": "knowledge"
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax ranked pages to return. Default 10, hard cap 50.
topicYesFree-text topic. Tokenized and matched against page filename, frontmatter aliases, frontmatter tags, summary, and body — in that order, with descending weight.
wikiRootNoPer-call wiki directory override.
vaultPathNoPer-call vault override.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Addedv0.3.5
  2. Removedv0.3.4
  3. Changed4 schema fields changedv0.3.2
    • addedInput schema / properties / limit / description
      Added value: +"Max ranked pages to return. Default 10, hard cap 50."
    • addedInput schema / properties / topic / description
      Added value: +"Free-text topic. Tokenized and matched against page filename, frontmatter aliases, frontmatter tags, summary, and body — in that order, with descending weight."
    • addedInput schema / properties / vaultPath / description
      Added value: +"Per-call vault override."
    • addedInput schema / properties / wikiRoot / description
      Added value: +"Per-call wiki directory override."
  4. Changed1 schema field changedv0.1.2
    • addedOutput schema / description
      Added value: +"Freeform object. The specific shape depends on the tool; see the tool description."
  5. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

While annotations already declare readOnlyHint=true and destructiveHint=false, the description adds substantial behavioral context: the weighting order (filename > aliases > tags > summary > body), the return shape (`{path, type, score, hitFields}`), and the dynamic vault resolution logic. It explicitly states 'Read-only; never writes,' consistent with annotations and goes beyond them by disclosing internal ranking mechanics.

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 well-structured with a clear lead sentence, explicit usage guidance, a dedicated paragraph on vault behavior, and two illustrative JSON examples. Every sentence serves a purpose, and the information density is high without being verbose. The front-loaded purpose allows quick scanning.

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

Completeness5/5

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

Given the tool's complexity (4 parameters, output schema present, dynamic vault context), the description covers all necessary aspects: operational scope, ranking logic, return format, vault selection, and alternatives. It also includes concrete examples that demonstrate typical usage. An agent can invoke this tool correctly after reading the description alone.

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 documentation already covers all four parameters at 100% coverage, which establishes a baseline of 3. The description adds marginal value by clarifying the default limit, hard cap, and the per-call override semantics for `wikiRoot` and `vaultPath`. The examples further reinforce parameter usage. This slightly exceeds baseline without being redundant.

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 opens with a specific verb ('Rank'), a clear resource ('wiki pages'), and a precise scope ('Sources/Concepts/Entities pages'). It immediately distinguishes itself from siblings by naming the alternatives (`wiki.lint`, `notes.search`) and their different purposes, making selection unambiguous.

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

Usage Guidelines5/5

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

Explicitly states when to use ('what does the wiki know about X?'), what to use instead (`wiki.lint` for whole-vault audits, `notes.search` for raw full-text search), and explains vault selection behavior. This covers both use cases and exclusions, leaving no room for misinterpretation.

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

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/bezata/kObsidian'

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