Read a Microsoft Word .docx document and return its paragraphs with 1-based indices.

Use this before docx_edit: the returned paragraph index is the address every edit operation uses. Each paragraph reports its text, its style id (e.g. Heading1), and whether it sits inside a table. Runs are merged, so text that Word split across formatting runs still reads as one continuous string.

Modes:

• text (default): every paragraph in document order.

• outline: only styled paragraphs (headings, titles) — use it for a quick structural overview.

• tables: only paragraphs inside table cells.

Large documents are paged: pass from/to to move through them, and check truncated in the result. This tool only reads. To change the document, follow up with docx_edit.

Apply edits to a Microsoft Word .docx document and write the result back.

Call docx_read first to learn paragraph indices. All index values refer to the ORIGINAL document as docx_read reported it — operations are applied together, so earlier operations never shift the indices of later ones.

Operations:

• {op:"replace_text", find, replace, all?} — replace text inside a paragraph, matching across formatting runs so the surrounding formatting is preserved. Works on the whole document unless you set all:false, in which case only the first occurrence is replaced. A match spanning a tab or line break is refused; use replace_paragraph for those.

• {op:"replace_paragraph", index, text} — replace one paragraph's whole text, keeping the formatting of its first run.

• {op:"insert_paragraph_after", index, text, style?} — insert a new paragraph after the given index; use index 0 to insert at the very start. style takes a style id such as Heading1.

• {op:"delete_paragraph", index} — remove a paragraph (inside a table it becomes an empty one, because a table cell must keep at least one paragraph).

• {op:"set_metadata", title?, subject?, creator?, keywords?, description?, lastModifiedBy?} — update the document properties.

By default the file is modified in place, and the first in-place edit leaves a one-time backup next to it as ".orig.docx". Pass output_path to write elsewhere instead, or dry_run:true to see what would change without writing anything.

Create a new Microsoft Word .docx document from plain text.

Each paragraph is either a string, or an object {text, style} where style is a Word style id such as Heading1, Heading2 or Title. The produced file is a valid OOXML package that opens in Word, WPS and LibreOffice.

Fails if the target path already exists — pick another path instead of overwriting by accident.

Open a PDF and report what it is: page count, document metadata, whether it has a real text layer, and its table of contents.

Call this first, before pdf_read or pdf_render_page. It tells you which reading strategy works:

• hasTextLayer true → pdf_read returns the actual text, page by page.

• scanned true → the pages are images with no text at all. pdf_read cannot help; use pdf_render_page to render pages and read them visually.

The returned toc lists top-level entries with the page each one starts on, so you can jump straight to the chapter a question is about instead of paging through the document.

Read a PDF's table of contents (bookmarks) as a flat list with real page numbers.

This is the navigation index for reading: each entry has a 1-based index, a depth (1 = top level), its title, and the 1-based page it starts on. Use it to find the section that covers a topic, then read or render just those pages.

Not every PDF has a usable outline — a scanned book often does, a print-to-PDF rarely does. When total is 0, fall back to pdf_read or pdf_render_page over page ranges.

Read the text of a PDF, page by page, with the page layout reconstructed into paragraphs.

Returns 1-based page numbers with their text. Headings are marked with a leading "# " so the structure of the page is visible. Pages are paged: pass from/to to move through the document.

This only works on PDFs that carry a text layer. If the PDF is a scan (pdf_info reports scanned: true), there is no text to extract and this tool refuses — render the pages with pdf_render_page and read them as images instead.

For a scanned PDF you can still use pdf_outline to learn which page a chapter starts on, then pass that page to pdf_render_page.

Render one page of a PDF as an image and return it for you to look at.

This is how you read a scanned PDF, and how you see anything that plain text cannot carry: figures, block diagrams, circuit drawings, tables, equations, page layout, handwriting.

The rendered page is returned as an actual image, so you see exactly what is on it.

Options:

• scale zooms. Omit it and the page is rendered at a width that keeps body text legible. Use 2–3 when small text or a dense diagram matters.

• region renders only part of the page, as fractions of the page from the top-left, e.g. {x:0.5,y:0.1,w:0.5,h:0.3} for the top-right quadrant. Combine with a larger scale to zoom into one figure or equation. Prefer this over rendering a whole page at a huge scale, which wastes the image budget on whitespace.

• out_path also writes the PNG to a file, when you need an artifact on disk.

To read a run of pages, call this once per page. Do not try to read a 400-page book end to end: use pdf_outline to find the relevant section and render only those pages.