Skip to main content
Glama

read_daily_note_full

Access complete daily notes with all content and sections for analysis, summarization, or information extraction from any part of the document.

Instructions

Read the entire daily note including all content and sections.

This gives you complete access to the note for analysis, summarization, or extracting information from any section.

Args: date_str: Optional date in YYYY-MM-DD format (defaults to today)

Returns: Full note content with metadata and all sections

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
date_strNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The core logic for reading the full daily note content, interacting with the vault and formatting the result.
    async def read_daily_note_full(date_str: str = None) -> str:
        """Read the entire daily note including all content and sections.
    
        Args:
            date_str: Optional date in YYYY-MM-DD format (defaults to today)
    
        Returns:
            Full note content with metadata and all sections
        """
        vault = get_vault()
        if not vault:
            return "❌ Obsidian vault not configured."
    
        if date_str:
            try:
                date = datetime.strptime(date_str, "%Y-%m-%d")
            except ValueError:
                return f"❌ Invalid date format: {date_str}"
        else:
            date = datetime.now()
    
        note_data = vault.read_full_note(date)
    
        if not note_data:
            return f"❌ No daily note found for {date.strftime('%Y-%m-%d')}."
    
        result = f"📖 Daily Note: {note_data['path']}\n\n"
    
        # Show metadata
        if note_data["metadata"]:
            result += "**Metadata:**\n"
            for key, value in note_data["metadata"].items():
                result += f"  {key}: {value}\n"
            result += "\n"
    
        # Show all sections
  • The MCP tool registration for 'read_daily_note_full', which calls the handler in daily_notes.py.
    @mcp.tool()
    async def read_daily_note_full(date_str: str = None) -> str:
        """Read the entire daily note including all content and sections.
    
        This gives you complete access to the note for analysis, summarization,
        or extracting information from any section.
    
        Args:
            date_str: Optional date in YYYY-MM-DD format (defaults to today)
    
        Returns:
            Full note content with metadata and all sections
        """
        return await daily_notes.read_daily_note_full(date_str)
Behavior3/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. It discloses the return value structure ('Full note content with metadata and all sections') and default parameter behavior ('defaults to today'). However, it omits error handling (what happens if the note doesn't exist?), side effects, or performance characteristics.

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 efficiently structured with a clear opening statement, followed by value proposition, then explicit Args and Returns sections. Every sentence earns its place without redundancy.

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?

Given that an output schema exists (per context signals), the brief return description is sufficient. The single optional parameter is well-documented in the description. It could be improved by mentioning error cases (e.g., missing notes) or authentication requirements.

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?

With 0% schema description coverage (the date_str property lacks a description field), the description adequately compensates by specifying the format ('YYYY-MM-DD') and default behavior ('defaults to today'). It successfully adds necessary semantic meaning missing from the structured schema.

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 'Read[s] the entire daily note including all content and sections' — specific verb (Read) + resource (daily note) + scope (entire vs partial). The phrase 'complete access' and 'all sections' effectively distinguishes it from the sibling 'read_daily_note_section'.

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 provides use cases ('analysis, summarization, or extracting information'), implying when to use it. However, it lacks explicit guidance on when NOT to use it versus the sibling 'read_daily_note_section' for targeted section access, or prerequisites like note existence.

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/94aharris/coach-ai'

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