Skip to main content
Glama

read_daily_note_section

Extract specific sections like Notes or Tasks from daily notes to quickly access organized information without reading entire documents.

Instructions

Read a specific section from the daily note.

Use this to read any section by name, such as "Notes", "Tasks", "Focus for Today", etc.

Args: date_str: Optional date in YYYY-MM-DD format (defaults to today) section: Name of the section to read (without ## or emoji)

Returns: Content of that section

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
date_strNo
sectionNoNotes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The implementation of the logic to read a daily note section.
    async def read_daily_note_section(date_str: str = None, section: str = "Notes") -> str:
        """Read a specific section from the daily note.
    
        Args:
            date_str: Optional date in YYYY-MM-DD format (defaults to today)
            section: Name of the section to read
    
        Returns:
            Content of that section
        """
        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()
    
        section_content = vault.read_section(date, section)
    
        if section_content is None:
            return f"❌ Section '{section}' not found in daily note for {date.strftime('%Y-%m-%d')}."
    
        return f"## {section}\n\n{section_content}"
  • The tool registration using the @mcp.tool() decorator.
    @mcp.tool()
    async def read_daily_note_section(date_str: str = None, section: str = "Notes") -> str:
        """Read a specific section from the daily note.
    
        Use this to read any section by name, such as "Notes", "Tasks",
        "Focus for Today", etc.
    
        Args:
            date_str: Optional date in YYYY-MM-DD format (defaults to today)
            section: Name of the section to read (without ## or emoji)
    
        Returns:
            Content of that section
        """
        return await daily_notes.read_daily_note_section(date_str, section)
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses input format constraints (YYYY-MM-DD, 'without ## or emoji') and the return value, but omits error handling (what happens if the section doesn't exist?), side effects, or permission requirements.

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 one-line summary, usage context, Args block, and Returns block. No redundant information; every sentence adds value beyond the structured fields.

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 two-parameter read operation with an output schema available, the description is adequate. It compensates well for the schema's lack of descriptions, though it could be improved by mentioning error conditions or the 'Notes' default value.

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?

Despite 0% schema description coverage, the Args section effectively documents both parameters: date_str includes format and default behavior ('today'), and section includes formatting constraints. Deducted one point for failing to document that the section parameter defaults to 'Notes'.

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 specific action ('Read') and resource ('specific section from the daily note'), distinguishing it from sibling tools like read_daily_note_full. Concrete examples ('Notes', 'Tasks', 'Focus for Today') further clarify the scope.

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?

While it provides examples of valid section names, it lacks explicit guidance on when to use this tool versus alternatives (e.g., 'use read_daily_note_full to retrieve the entire note'). The usage guidance is implied but not directive.

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