konbu

Create a calendar event with a fixed start time (and optional end time). Use this for time-bound items such as meetings or appointments; use create_todo for deadline-style tasks without a specific time, and create_memo for free-form notes. Returns the created event with its assigned UUID. Example: {"title":"Dentist","start_at":"2026-06-15T13:00:00+09:00","end_at":"2026-06-15T14:00:00+09:00","tags":["health"]} → {"id":"...","title":"Dentist",...}. Side effects: writes a new record on each call — calling twice creates two events. Not idempotent.

Create a new memo (free-form Markdown note) in the konbu planner. Returns the created memo with its assigned UUID. Use this for notes without a due date or completion state; use create_todo for actionable tasks, and create_event for time-bound calendar items. Example: {"title":"Q3 plans","content":"## Goals\n- ship MCP","tags":["work","planning"]} → {"id":"...","title":"Q3 plans",...}. Side effects: writes a new record on each call — calling twice creates two memos. Not idempotent.

Create a new todo (actionable task) in the konbu planner. Returns the created todo with its assigned UUID and status="open". Use this for tasks that need completion tracking; use create_memo for free-form notes, and create_event for items with a specific start time. Example: {"title":"Buy groceries","due_date":"2026-06-01","tags":["shopping"]} → {"id":"...","title":"Buy groceries","status":"open",...}. Side effects: writes a new record on each call — calling twice creates two todos. Not idempotent.

Permanently delete a calendar event by ID. This action cannot be undone. Example: {"id":"ghi09876"} → "deleted". Side effects: destructive, irreversible. The first call deletes; subsequent calls with the same id error.

Permanently delete a memo by ID. This action cannot be undone. Returns the string "deleted" on success. Example: {"id":"abc12345"} → "deleted". Side effects: destructive, irreversible. The first call deletes; subsequent calls with the same id error because the memo no longer exists.

Permanently delete a todo by ID. This action cannot be undone. Prefer mark_todo_done if you only want to record completion — completed todos remain searchable and visible in history. Example: {"id":"def67890"} → "deleted". Side effects: destructive, irreversible. The first call deletes; subsequent calls with the same id error.

Fetch the full details of a single calendar event by ID, including description, all-day flag, and tags. Example: {"id":"ghi09876"} → {"id":"ghi09876-...","title":"...","description":"...","start_at":"...","end_at":"...","all_day":false,"tags":[...]}. Side effects: read-only. Errors if the id does not exist.

Fetch the full details of a single memo by ID, including the Markdown content body. Typically called after list_memos or search to read a memo's body. Example: {"id":"abc12345"} returns {"id":"abc12345-...","title":"...","content":"# heading...","tags":[...]}. Side effects: read-only. Errors if the id does not exist or belongs to another user.

Fetch the full details of a single todo by ID, including description, status, due date, and tags. Example: {"id":"def67890"} → {"id":"def67890-...","title":"...","description":"...","status":"open","due_date":"2026-06-01","tags":[...]}. Side effects: read-only. Errors if the id does not exist.

List calendar events belonging to the user, ordered by start time. Returns id, title, start_at, end_at, all_day flag, and tags for each event. For tasks without a fixed time use list_todos; for free-form notes use list_memos. Example: returns [{"id":"ghi09876-...","title":"Standup","start_at":"2026-05-28T10:00:00+09:00","end_at":"2026-05-28T10:15:00+09:00","all_day":false,"tags":["work"]}, ...]. Workflow: typically followed by get_event(id) for full details or update_event(id, ...) to reschedule. Side effects: read-only.

List all memos (free-form Markdown notes) belonging to the user, newest first. Returns id, title, tags, and timestamps for each memo, but NOT the full Markdown body — call get_memo to read a specific memo's body. Memos have no status or due date; for actionable tasks use list_todos. Example: returns [{"id":"abc12345-...","title":"Daily notes","tags":["work"],"created_at":"2026-05-27T..."}, ...]. Workflow: typically followed by get_memo(id) when the user wants to read a specific memo's content. Side effects: read-only.

List all todos (actionable tasks with status and optional due date), newest first. Returns id, title, status (open / done), due_date, and tags for each todo. For free-form notes without status use list_memos; for time-bound calendar items use list_events. Example: returns [{"id":"def67890-...","title":"Buy groceries","status":"open","due_date":"2026-06-01","tags":["shopping"]}, ...]. Workflow: typically followed by mark_todo_done(id) when the user reports completion, or get_todo(id) to read the full description. Side effects: read-only.

Mark a todo as completed (status="done"). Convenience shortcut for the most common state transition; equivalent to update_todo with status="done" but communicates intent more clearly. Returns the string "marked as done" on success. Example: {"id":"def67890"} → "marked as done". Side effects: idempotent — calling on an already-completed todo is a no-op that still returns success.

Reopen a completed todo (transition status from "done" back to "open"). Use this when the user wants to undo a completion. Returns the string "reopened" on success. Example: {"id":"def67890"} → "reopened". Side effects: idempotent — calling on an already-open todo is a no-op that still returns success.

Search across memos, todos, and calendar events by keyword. Use when the user asks an open-ended question like "find anything about X" or doesn't specify the resource type. Returns a unified result list with each match tagged by its resource kind (memo / todo / event). For listing every item of a specific kind use list_memos / list_todos / list_events instead. Example: {"query":"meeting notes"} matches items whose title, body, description, or tags contain both "meeting" AND "notes" (whitespace is AND, case-insensitive substring match). Side effects: read-only, safe to retry.

Update an existing calendar event. Only the fields provided are modified; omitted fields are left unchanged. The tags array (if provided) REPLACES the existing tag set. Returns the updated event. Example: {"id":"ghi09876","start_at":"2026-06-16T13:00:00+09:00","end_at":"2026-06-16T14:00:00+09:00"} reschedules the event by one day. Side effects: idempotent for the same input; only specified fields change. Errors if the id does not exist.

Update an existing memo's title, content, and/or tags. Only the fields provided are modified; omitted fields are left unchanged. Note that the tags array (if provided) REPLACES the existing tag set — pass the full desired list, not a delta. Returns the updated memo. Example: {"id":"abc12345","title":"New title"} renames the memo and leaves content/tags untouched. Side effects: idempotent for the same input; only specified fields change. Errors if the id does not exist.

Update an existing todo's fields. Only the fields provided are modified; omitted fields are left unchanged. For toggling completion state alone, prefer mark_todo_done / reopen_todo for clearer intent; use update_todo when you also need to change title, description, due_date, or tags. The tags array (if provided) REPLACES the existing tag set. Example: {"id":"def67890","due_date":"2026-07-01","description":"Updated context"} changes only those two fields. Side effects: idempotent for the same input; only specified fields change. Errors if the id does not exist.