Skip to main content
Glama
Sign In
Obsidian MCP Server

Obsidian MCP Server

by aniketbiswas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_daily_note

Retrieve today's daily note content, creating the note if it doesn't exist, to stay organized with your daily entries.

Instructions

Get the content of today's daily note. Creates the note if it doesn't exist (using Obsidian's daily notes settings). Requires Daily Notes core plugin or Periodic Notes plugin.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_daily_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
includeContentNoWhether to include the full content.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well by disclosing the non-obvious side effect 'Creates the note if it doesn't exist' and the dependency on Daily Notes or Periodic Notes plugins. It stops short of describing the exact return format, but the core behavior is transparent.

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?

Two concise sentences deliver the purpose, the create-on-missing behavior, and the plugin requirement without wasted words. The description is front-loaded with the primary action.

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?

For a simple tool with one optional parameter, the description covers the purpose, creation side effect, and prerequisites. It does not detail return values, but the absence of an output schema lowers that burden. Minor gap: no mention of error behavior when plugins are absent.

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 fully describes the only parameter includeContent with a clear explanation, so the schema does the heavy lifting. The description adds no additional parameter context, matching the baseline for 100% 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 opens with 'Get the content of today's daily note,' clearly stating the verb and resource. It also notes that it creates the note if missing, distinguishing it from general read_note and placing it in the daily-note context.

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 description implies use for today's daily note and notes the plugin requirement, but it does not explicitly contrast with siblings like read_note or get_periodic_note. There is no when-not or alternative guidance, only a prerequisite.

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