Obsidian MCP Server

create_todo

Add a new task to your Obsidian notes by creating or updating a TODO list with details like priority, due date, and project.

Instructions

Create or add a TODO item. Can create a new TODO note or append to existing TODO list.

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": {
      "task": "<task>"
    },
    "name": "create_todo"
  }
}

Input Schema

Name	Required	Description
`task`	Yes	The TODO task description
`project`	No	Project name for organization
`priority`	No	Task priority
`due_date`	No	Due date (YYYY-MM-DD format)
`context`	No	Additional context about the task
`todo_file`	No	Path to TODO file (default: 'TODOs.md')

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jan 20, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries full burden but offers limited behavioral insight. It mentions the tool can 'create or add' and 'append to existing TODO list', but doesn't disclose permissions needed, whether it overwrites or merges content, error handling, or file system implications. For a mutation tool with zero annotation coverage, this is insufficient.

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 concise with two clear sentences that efficiently convey the core functionality. However, the second sentence slightly repeats the first ('create' vs 'create or add'), and it could be more front-loaded with critical distinctions.

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

Completeness2/5

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

For a mutation tool with 6 parameters, no annotations, and no output schema, the description is incomplete. It lacks essential context like required permissions, file path defaults/behavior, error scenarios, and what 'append' means operationally. The agent would struggle to use this tool confidently.

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 fully documents all 6 parameters. The description adds no parameter-specific information beyond the generic 'create or add' context, which doesn't enhance understanding of individual parameters. Baseline 3 is appropriate when the schema does all the work.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('create or add') and resource ('TODO item'), specifying it can create new items or append to existing lists. However, it doesn't distinguish this tool from sibling tools like 'append_to_note' or 'write_note' which might have overlapping functionality.

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 provides minimal guidance by mentioning 'create or add' and 'append to existing TODO list', but offers no explicit when-to-use rules, prerequisites, or comparisons to alternatives like 'append_to_daily_note' or 'write_note'. This leaves the agent with unclear decision boundaries.

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

Deploy Server