Skip to main content
Glama
AdrianV101

obsidian-pkm

by AdrianV101

vault_query

Query Obsidian notes by frontmatter metadata (type, status, tags, dates, custom fields) with sorting and folder limits. Results include clickable links to open notes in Obsidian.

Instructions

Query notes by YAML frontmatter metadata (type, status, tags, dates, custom fields, sorting). Paths in this tool's output are formatted as markdown links [vault-relative-path.md](obsidian://...) so users can Cmd/Ctrl-click to open in Obsidian. Preserve the link form when relaying paths to the user; pass only the bracket text (e.g. 01-Projects/Foo/note.md) to other vault tools' path arguments, never the full markdown link.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoALL tags must be present (case-insensitive)
typeNoFilter by note type (exact match)
limitNoMax results to return
folderNoLimit search to this folder (supports partial names, e.g. 'MyApp')
statusNoFilter by status (exact match)
sort_byNoSort results by this frontmatter field. Smart ordering: priority uses rank (urgent>high>normal>low), dates sort chronologically, others alphabetically. Nulls sort last.
tags_anyNoANY tag must be present (case-insensitive)
sort_orderNoSort direction (default: asc)asc
created_afterNoNotes created on or after this date (YYYY-MM-DD)
custom_fieldsNoFilter by arbitrary frontmatter fields (exact match). Use null to match missing fields.
created_beforeNoNotes created on or before this date (YYYY-MM-DD)
Behavior4/5

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

No annotations exist, so the description carries the burden. It discloses a key behavioral trait: output paths are markdown links with instructions on how to handle them. This goes beyond the schema, though it does not explicitly state read-only behavior (implied by 'Query').

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?

Three sentences: the first states the purpose, the second and third explain a unique output format and usage rule. No wasted words, information is front-loaded.

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

Completeness4/5

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

With no output schema, the description partially explains return values by revealing the link format and how to use paths. It lacks an explicit statement of full return structure, but for a query tool, this is sufficient given the detailed input schema and the tool's simple output concept.

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?

Schema coverage is 100%, so the baseline is 3. The description does not add parameter-specific meaning beyond listing categories already in the schema. The link-handling note is about output, not parameters, so no extra semantic value for params is provided.

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's action and resource: 'Query notes by YAML frontmatter metadata', listing key filter fields. This differentiates it from siblings like vault_search (full-text) by emphasizing metadata-based querying.

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

Usage Guidelines4/5

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

The description implies usage for metadata-based queries, which provides clear context. It also gives specific handling instructions for output paths (preserve link form, pass bracket text to other tools), but does not explicitly exclude alternatives or mention when to use a different tool.

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

Install Server

Other Tools

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/AdrianV101/obsidian-pkm-plugin'

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