Search the default Outlook calendar folder by date range and/or subject substring. At least one of from/to/subject is required. A subject-only query (no explicit from/to) auto-applies a default window — 90 days back, 365 days forward from now, configurable via calendar_subject_search_lookback_days/..._lookahead_days — since a calendar's value is mostly ahead of today; the window actually used is echoed back as windowApplied in the response. Supplying explicit from/to overrides this window entirely (they can widen or narrow the search — caller-controlled). limit bounds the number of rows returned (optional, default 50, hard max 200 — over-max is clamped, not rejected; <= 0 is rejected).

Fetch full detail (including body) for a single event by its Outlook entryId.

Resolve the single note-appointment matching date+subject and return its full detail (subject + body).

Search the default Outlook Tasks folder. All filters are optional; a filterless call returns every task in the folder (up to the effective limit). limit bounds the number of rows returned (optional, default 50, hard max 200 — over-max is clamped, not rejected; <= 0 is rejected).

Fetch full detail (including body) for a single task by its Outlook entryId.

Search the default Outlook Inbox, Sent Items, or Drafts folder (folder), or an arbitrary custom folder resolved from the default mail store's root (folderPath, a /-delimited path) — exactly one of folder/folderPath is required. Also filters by date range, subject substring, and/or sender substring; at least one of dateFrom/dateTo/subject/sender is required. limit bounds the number of rows returned (optional, default 50, hard max 200 — over-max is clamped, not rejected; <= 0 is rejected).

Fetch full detail (including body) for a single Inbox/Sent Items/Drafts/folderPath message by its Outlook entryId. attachmentNames is always populated; htmlBody is populated only when includeHtmlBody=true is passed (default false).

Search by a case-insensitive filename substring (answered by a bounded filesystem walk, independent of the Windows Search index) and/or a full-text phrase match (answered by the index: ADO, then a PowerShell bridge on ADO failure), optionally restricted to an absolute scope subtree. At least one of filename/phrase is required; scope (if given) must fall within a configured or default allowed search root. Returns results plus a resultsTruncated flag.

Fetch full indexed metadata for a single file by its native path or file:///-style URL form, as previously returned by file_search. path must fall within a configured or default allowed search root.

Full-text search over OneNote page content (FindPages via the COM bridge). query must be non-empty — rejected as an [invalid_request] error before any adapter call. limit bounds the number of rows returned (optional, default 50, hard max 200 — over-max is clamped, not rejected; <= 0 is rejected). An empty result is [], not an error.

Fetch full, read-only text detail for a single OneNote page by its pageId (as returned by onenote_search). Never mutates any notebook/section/page state.

bodyText is a FLATTENED plain-text reading view of the page — bullets, indentation, tables and images render as plain lines. It is not the storage format: onenote_update_page appends and never writes this flattened text back over the page, so reading a formatted page is always safe. bodyTextIncomplete: true means the page contains tables, images or ink that this flattened view cannot represent — the page holds more than you are seeing; updating it is still safe. lastModifiedDateTime is the value onenote_update_page's conflict guard expects — pass it back exactly as returned.

List every OneNote notebook/section pair with its canonical ids. sectionId (the {GUID}{1}{B0} form) is what onenote_create_page requires — a bare GUID or a section NAME will never resolve. Read-only; never mutates any state.

Create a new page in the OneNote section identified by sectionId — the canonical {GUID}{1}{B0} form returned by onenote_list_sections (also on onenote_search rows); a bare GUID or a section name will never resolve. bodyText is written as one plain-text paragraph. The section's owning notebook is resolved and checked against the writable-notebook allowlist (onenote_writable_notebooks, default ["z - Test Notebook"]) before any write is attempted — refused with a clear [onenote_notebook_not_allowed] error otherwise.

APPEND bodyText as one new plain-text paragraph at the end of the OneNote page identified by pageId. Never replaces or reformats existing content — the page's original formatting (bullets, tables, images) is preserved untouched, so updating a formatted page is safe.

dateExpectedLastModified is a conflict guard, not a write-back of the read body: pass lastModifiedDateTime exactly as onenote_get_page returned it, and a mismatch (the page changed since your read) raises [onenote_page_conflict] — re-read and retry with the fresh value. OMIT the field for an UNGUARDED overwrite (no concurrency check at all): the escape hatch for a page that keeps rejecting a freshly-read value, which OneNote's lazily-stamped timestamps can cause on pages not written recently. The page's owning notebook is checked against the writable-notebook allowlist before any write, same as onenote_create_page.

Identify this deployment: package name, build UTC and build id from the build stamp (build-info.json; null with a note for a source checkout or a pre-stamp package), install root (distinguishes the PRO and QA installs), Python version, and the tool names this server process actually registered. Read-only, touches no Outlook/OneNote/file state. Call it FIRST when verifying that a redeployed build is the one answering — a server started before a promote keeps running the old code until its client restarts.