markdown-vault-mcp

Overview Schema Source Related Servers Discussions Admin

log_to_daily_note

Append a timestamped log message to the Logs section of today's daily note, keeping chronological entries organized in your markdown vault.

Instructions

Append a log entry to the 'Logs' section of today's daily note.

Format: - HH:MM: Content

Args: log_message: The log message to append.

Returns: Success message or error description.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "log_message": "<log_message>"
    },
    "name": "log_to_daily_note"
  }
}

Input Schema

Name	Required	Description	Default
`log_message`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.1Sep 6, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Since no annotations are provided, the description carries the full behavioral disclosure burden. It clearly indicates a write operation ('Append') and gives the exact inserted format, but it does not disclose whether the daily note or Logs section is created on demand, whether HH:MM is automatically generated from current time, or how repeated appends behave.

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 compact and well-structured: a purpose sentence, a format line, then Args/Returns. It is front-loaded with the most important information, and the format example provides concrete value without unnecessary prose.

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

Completeness3/5

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

The output schema covers return values, so that part is not a gap. However, edge-case behavior such as creation of a missing daily note or Logs section and automatic timestamp generation is unstated, which could lead to incorrect calls in valid use cases. For a simple appending tool, this is adequate but not fully complete.

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?

Schema coverage is 0%, so the description must explain log_message on its own. It does so with a clear definition ('The log message to append') and a format example showing where the content lands. This fully resolves the meaning of the single parameter.

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 a specific verb ('Append') and resource ('Logs' section of today's daily note), with an explicit format template. It is easy to distinguish from siblings like append_to_daily_note or run_macro because it names the exact target and content shape.

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

Usage Guidelines2/5

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

The description does not provide any guidance on when to use this tool versus nearby alternatives such as log_to_note or append_to_daily_note. The usage context is implied by the name and target, but no explicit conditions or exclusions are given, leaving an agent to guess which sibling fits a non-obvious scenario.

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