Skip to main content
Glama
Sign In
obsidian-mcp

obsidian-mcp

by ZethicTech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

daily_prepend

Prepend text to today's daily note after frontmatter. Quickly add tasks, ideas, or updates to the top of your daily log.

Instructions

Prepend content to today's daily note (after frontmatter).

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": {
      "content": "<content>"
    },
    "name": "daily_prepend"
  }
}

Input Schema

NameRequiredDescriptionDefault
contentYesContent to prepend (use \n for newlines)
inlineNoPrepend inline (no newline after)
paneTypeNoHow to open the note
openNoOpen note after prepending

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.7

TDQS

A3.6/5.0
Behavior3/5

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

Annotations provide minimal hints (readOnlyHint=false, destructiveHint=false, idempotentHint=false). The description adds the important detail that content is prepended after frontmatter, but does not disclose other behaviors such as whether the note is created if it doesn't exist or what happens to existing content beyond prepending.

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 a single sentence, concise and front-loaded with the key action. Every word serves a purpose with no 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?

The tool has no output schema, so return value explanation is unnecessary. The description covers the core action and a key detail (after frontmatter), but could be more explicit about prerequisites (e.g., whether the daily note must exist or is created) given sibling tools like 'daily_create' exist.

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?

Schema description coverage is 100%, so the schema already documents all parameters. The description does not add extra meaning beyond what the schema provides, meeting the baseline for high 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 clearly states the verb (prepend), resource (today's daily note), and a specific qualifier (after frontmatter). It effectively distinguishes from sibling tools like 'daily_append' (which appends) and 'prepend_note' (which prepends to any note).

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?

No explicit guidance on when to use this tool versus alternatives like 'daily_append' or 'prepend_note'. The description implies a specific use case (prepending to today's daily note) but does not provide context for when to choose this over siblings.

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