LibreOffice MCP Tools

document_apply_style

Apply heading or paragraph styles to specific paragraphs in LibreOffice documents to format text consistently and structure documents efficiently.

Instructions

Apply a heading or paragraph style to a specific paragraph by index.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "docId": "<docId>",
      "paragraphIndex": "<paragraphIndex>",
      "style": "<style>"
    },
    "name": "document_apply_style"
  }
}

Input Schema

Name	Required	Description
`docId`	Yes	Document handle returned by document_open
`paragraphIndex`	Yes	Index of the paragraph to style (0-based)
`style`	Yes	Style to apply (e.g., Heading 1, Heading 2, Heading 3, Heading 4, Heading 5, Heading 6, Normal)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Apr 21, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action but doesn't reveal whether this is a destructive mutation (likely yes, but not confirmed), what permissions are needed, how errors are handled (e.g., invalid index), or the response format. This leaves significant gaps for a tool that modifies document content.

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?

The description is a single, efficient sentence that directly states the tool's purpose without any fluff or redundancy. It's appropriately sized and front-loaded, making it easy for an agent to parse quickly.

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

Completeness2/5

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

Given the tool's complexity (a mutation operation with no annotations and no output schema), the description is insufficient. It lacks details on behavioral traits (e.g., side effects, error handling), output expectations, and usage context, making it incomplete for safe and effective agent invocation.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents all three parameters (docId, paragraphIndex, style) with clear descriptions. The description adds no additional parameter semantics beyond implying that 'style' includes heading and paragraph types, which is already suggested by the schema's example values. This meets the baseline for high schema coverage.

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

Purpose4/5

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

The description clearly states the action ('Apply a heading or paragraph style') and target ('to a specific paragraph by index'), which is a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like document_replace_text or document_insert_paragraph, which might also affect paragraph formatting, so it doesn't reach the highest score.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an open document), exclusions, or comparisons to other styling-related tools that might exist in the context, leaving the agent to infer usage from the tool name alone.

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