Skip to main content
Glama
emguide

Headless Obsidian MCP

by emguide

resolve_daily_note

Resolve a calendar date to its Obsidian daily-note path, using configured folder and format. Returns the path, existence status, and template path.

Instructions

Map a calendar date to its canonical daily-note path, using the Daily Notes core plugin's own configuration (.obsidian/daily-notes.json: folder, format, template; OBSIDIAN_DAILY_FOLDER overrides the folder). Returns { date, path, exists, template }: date is the resolved ISO day, path the canonical note path (no .md; slashes in the configured format nest folders, as in Obsidian), exists whether the note is on disk, template the configured daily template path or null. Read-only — existing tools do the rest: apply_template (which accepts the returned template path) or write_note to create it, append_note/append_to_section to log into it, read_notes/read_section to read it. Errors when daily notes are not configured. Note: {{date}}/{{time}} in an applied template expand with the current moment, not the resolved day — exact Obsidian parity for today, a known caveat when creating past/future notes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNo"YYYY-MM-DD", or "today" (default) | "yesterday" | "tomorrow"
Behavior5/5

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

Despite no annotations, the description fully discloses behavioral traits: read-only operation, error conditions (when daily notes not configured), path format (no .md, slashes nest folders), and the template expansion caveat. This is comprehensive beyond what annotations would typically provide.

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

Conciseness4/5

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

The description is well-structured, starting with the main purpose, followed by return details, usage guidance, and a caveat. While slightly long, every sentence contributes meaning; a minor trim could improve conciseness.

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?

The description is fully complete for this tool: it explains output fields, error scenarios, and how it fits with sibling tools. No output schema is needed given the detailed return description.

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

Parameters5/5

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

The single parameter 'date' is fully described in the schema (100% coverage). The description adds value by listing accepted string values ('today', 'yesterday', 'tomorrow', 'YYYY-MM-DD') and the default behavior, enhancing the schema's meaning.

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 maps a calendar date to a canonical daily-note path using the Daily Notes plugin configuration. It specifies the verb 'map' and resource 'daily-note path', and distinguishes it from sibling tools like note resolution or file search.

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 tells when to use this tool (to get the path) and what to do next: 'existing tools do the rest: apply_template, write_note, append_note, etc.' It also mentions the caveat about template expansion for past/future dates, which guides appropriate usage.

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/emguide/headless-obsidian-mcp'

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