doc-control

Overview Schema Source Related Servers Discussions Admin

live_open

Attach to Word or LibreOffice for live editing: find and focus an open document window, or open the file in the selected app before live edits.

Instructions

Attach to Word or LibreOffice for live editing: find the window already holding the document, or open it in app (word or libreoffice; default the one reachable, see live.status) and bring it to the front (front: false keeps it behind). Call it before live.select, live.get_selection, live.save, live.close and doc.batch with engine live. Opens or focuses a window; never changes the document. ENGINE_UNAVAILABLE when no app can be driven, DOC_AMBIGUOUS when a file name matches several open documents.

Input Schema

Name	Required	Description
`app`	No	`word` or `libreoffice`.
`doc`	Yes	Path to the document, or the file name of one open in a live app.
`front`	No	Bring the app's window to the front (default true); the reply's `front` says whether it came.
`engine`	No	Always the live engine; may be left out.

Output Schema

Name	Required	Description
`ok`	Yes	Always true on success.
`op`	Yes	The operation that ran.
`api`	Yes	API version (1.0).
`doc`	No	The document read or written: path, sha256 and paragraph count.
`next`	Yes	Cursor for the next page (pass as cursor), or null.
`result`	Yes	What the operation returns.
`warnings`	Yes	Things to know about the result.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.7.2Oct 15, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "api": {
+      "description": "API version (1.0).",
+      "type": "string"
+    },
+    "doc": {
+      "description": "The document read or written: path, sha256 and paragraph count.",
+      "properties": {
+        "characters": {
+          "description": "text.normalize of a text string: its length.",
+          "type": "integer"
+        },
+        "paragraphs": {
+          "description": "Body paragraphs.",
+          "type": "integer"
+        },
+        "path": {
+          "description": "Path of the document.",
+          "type": "string"
+        },
+        "sha256": {
+          "description": "sha256 of the file (pass as expect.sha256 to a write).",
+          "type": "string"
+        },
+        "source": {
+          "description": "A .txt/.md/.odt source's format, encoding and split mode; \"text\" for a text string (text.normalize).",
+          "type": [
+            "object",
+            "string"
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "next": {
+      "description": "Cursor for the next page (pass as cursor), or null.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "ok": {
+      "description": "Always true on success.",
+      "type": "boolean"
+    },
+    "op": {
+      "description": "The operation that ran.",
+      "type": "string"
+    },
+    "result": {
+      "description": "What the operation returns.",
+      "properties": {
+        "app": {
+          "description": "The app now attached (word or libreoffice).",
+          "type": "string"
+        },
+        "dirty": {
+          "description": "It has unsaved changes.",
+          "type": "boolean"
+        },
+        "front": {
+          "description": "With front: whether its window was brought to the front.",
+          "type": "boolean"
+        },
+        "path": {
+          "description": "Full path of the document.",
+          "type": "string"
+        }
+      },
+      "required": [
+        "app",
+        "path",
+        "dirty"
+      ],
+      "type": "object"
+    },
+    "warnings": {
+      "description": "Things to know about the result.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "api",
+    "ok",
+    "op",
+    "result",
+    "warnings",
+    "next"
+  ],
+  "type": "object"
+}

First observedv0.1.0Oct 15, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Adds real behavioral context beyond annotations: the error states ENGINE_UNAVAILABLE and DOC_AMBIGUOUS, the app-default resolution, and the assurance it 'never changes the document'. Annotations (readOnlyHint=false, destructiveHint=false) already sketch the safety profile, and the description is consistent with them.

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?

Front-loads the core action before the conditional and error clauses, and each sentence carries information. It is dense and slightly clause-heavy, but nothing is plainly redundant.

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

Completeness5/5

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

For a prerequisite/attach tool with an output schema already covering return values, it supplies prerequisites, error conditions, and sibling ordering. Nothing an agent needs to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds defaulting semantics the schema does not: 'app ... default the one reachable, see live.status' and 'front: false keeps it behind'. It enriches the two non-obvious parameters beyond their schema descriptions.

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

Purpose5/5

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

States a specific verb cluster (attach/find/open/focus) on a specific resource (the Word or LibreOffice window holding a document). It clearly distinguishes itself from the plain doc_open sibling by tying the operation to 'live editing' and window attachment.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly instructs to 'Call it before live.select, live.get_selection, live.save, live.close and doc.batch with engine live', naming both the prerequisites and the dependent siblings. The 'front: false keeps it behind' note and the 'see live.status' pointer give concrete alternative-selection context.

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

Deploy Server