Write tools

Tools that mutate the vault. Each returns a result describing what was written. The same business rules as the CLI apply (append-only notes, auto-logged project state, the project cap).

Logging, capture, triage

Tool	Inputs	Effect
`append_to_log`	`text`	Append a line to today’s daily note. (`cdno log`)
`capture`	`text`	Drop a raw note into `inbox/`. (`cdno capture`)
`discard_inbox_item`	`slug`	Clear a triaged capture (slug from `triage_inbox`).

Evidence

Tool	Inputs	Effect
`file_to_portfolio`	`portfolio`, `source`, `origin`, `content?`, `attach?`, `vars?`	File evidence into a portfolio; `attach` is a server-side path to a non-Markdown artefact (`vars` is ignored on the attach path). (`cdno file`)

Projects, actions, milestones, waiting-on

Tool	Inputs	Effect
`update_project_state`	`project`, `new_state`	Rewrite the Current State (auto-logs the previous).
`add_action`	`project`, `title`, `energy`, `with_note?`, `vars?`	Append a next action; `with_note` also scaffolds a manifest note (`vars` applies only then).
`promote_action`	`project`, `query`, `vars?`	Promote a bullet to a manifest note (substring match).
`complete_action`	`project`, `query`	Complete an action; archives its note if any.
`add_milestone`	`project`, `title`, `target_date`, `hard?`	Add a milestone; `hard` counts it in commitments.
`complete_milestone`	`project`, `query`	Complete a milestone (substring match).
`add_waiting_on`	`project`, `description`	Add a waiting-on blocker.
`resolve_waiting_on`	`project`, `query`	Resolve a waiting-on item (substring match).

Commitments and tracking

Tool	Inputs	Effect
`create_commitment`	`title`, `due`, `context`, `project?`, `stewardship?`, `vars?`	Create a standalone commitment note.
`complete_commitment`	`commitment` (slug)	Mark a commitment done and archive it.
`create_tracking_entry`	`stewardship`, `activity`, `routine?`, `content?`, `vars?`, `metrics?`, `date?`	File a tracking note under an expanded stewardship. `metrics` is a JSON object merged into the entry’s frontmatter — a scalar per reading (`{"balance": 1240.5}`), or an array of flat records when one entry holds several comparable items (`{"detail": [{"subject": "harmony", "minutes": 25}]}`); a scalar whose key is declared under `[schemas.tracking.fields]` is type-checked, and a key naming the note’s identity (`type`, `stewardship`, `activity`, `date`) is refused. `date` files the entry for a past day (bounded to 50 years back, 1 year ahead). A second call for the same `(activity, date)` merges into the first: content appended, metrics folded in. Records carrying a stable `id` replace the record with that `id`; records without one append, so re-sending a payload without ids double-counts summed metrics. Either way the write is journalled to today’s daily log.

Frontmatter

Tool	Inputs	Effect
`set_frontmatter`	`note`, `key`, `value`	Set a declared, `settable = true` typed frontmatter field through the index (no desync). `note` is `today`, a `YYYY-MM-DD` date, or a vault-relative path. Engine-owned keys (`type`, `status`, a period key) are rejected; the value is type-checked; `log_on_change` fields stamp a daily-log line. (`cdno frontmatter set`)

Daily, weekly, and monthly sections

Tool	Inputs	Effect
`upsert_daily_section`	`section` (`Standup`\|`Intention`\|`Agenda`\|`Meeting`), `content?`, `date?`, `append?`	Write or append a daily-note section.
`upsert_weekly_section`	`section` (`Wins`\|`Challenges`\|`One Improvement`\|`This Week's Goal`), `content?`, `date?`, `append?`	Write or append a weekly-note section.
`upsert_monthly_section`	`section` (`Wins`\|`Themes`\|`Next Month's Focus`), `content?`, `date?`, `append?`	Write or append a monthly-note section.

Notes

append? defaults to replacing the section; set it true to append instead.
Dates are YYYY-MM-DD; week-scoped tools accept any day in the target week, and month-scoped tools accept any day in the target month.
vars? is an optional name -> value map supplying values for a custom template’s [variables.prompt] placeholders — the MCP analogue of the CLI’s repeatable --var name=value. Omitting a required prompted variable fails with an “unresolved prompts” error. See Creation and lifecycle tools for the full list of templated tools that accept it.
See also: Creation and lifecycle tools, JSON output.

Keyboard shortcuts

Cuaderno