io.github.Anselmoo/mcp-ooxml-ledger

Overview Schema Source Related Servers Score Discussions Admin

Open document

open_document

Idempotent

Starts a tracked editing session for Office documents, resuming the existing session when the file is unchanged to prevent duplicate work.

Instructions

Start an editing session: unpack the document to disk, record its baseline digest and part manifest, and sweep expired sessions. Reopening the same unchanged document resumes its live session instead of forking a second one.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`document`	Yes
`ttl_seconds`	No
`keep_baseline`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`kind`	Yes
`name`	Yes
`canon`	Yes
`parts`	Yes
`swept`	Yes
`expires`	Yes
`resumed`	Yes
`document`	Yes
`session_id`	Yes
`swept_skipped`	Yes
`baseline_digest`	Yes
`baseline_stored`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 31, 2026

TDQS

A4/5.0

Behavior4/5

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

The description discloses meaningful side effects beyond annotations: unpacking the document, recording digest and manifest, sweeping expired sessions, and the idempotent resume behavior. This complements idempotentHint=true with concrete details.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two dense sentences, front-loaded with the primary purpose and followed by an important idempotency nuance. No filler, every clause adds useful information.

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

Completeness3/5

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

The output schema exists, so return values are not needed in the description. However, with three parameters, zero schema descriptions, and no explanation of ttl_seconds or keep_baseline, the description is not fully complete for invoking the tool correctly.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. It indirectly covers 'document' but says nothing about ttl_seconds or keep_baseline, leaving two parameters semantically unexplained. This is a significant gap.

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?

The description clearly states the tool's purpose with a specific verb and resource: 'Start an editing session' and describes concrete actions (unpack to disk, record baseline digest and part manifest). It is easily distinguishable from siblings like close_document and commit_document.

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

Usage Guidelines4/5

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

The description communicates clear context: call this to start an editing session, and reopening an unchanged document resumes the live session. It does not explicitly name exclusions or alternatives, but the intended usage moment is clear.

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

Install Server