local-mcp

Word Read

word_read

Read-only

Reads text content from a Word document (.docx file).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`path`	Yes	Absolute path to the .docx file
`force_download`	No	If the file is stored in the cloud and evicted from this Mac (dataless), request the download and wait for it instead of failing. Off by default: a download can take minutes and use metered data, so it is the caller's decision.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`text`	Yes	Extracted text content
`chars`	Yes	Number of characters in the extracted text

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 8, 2026

addedInput schema / properties / force_download

Added value: +{
+  "description": "If the file is stored in the cloud and evicted from this Mac (dataless), request the download and wait for it instead of failing. Off by default: a download can take minutes and use metered data, so it is the caller's decision.",
+  "type": "boolean"
+}

First observedJun 30, 2026

TDQS

A4/5.0

Behavior3/5

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

The description describes a read-only operation, and the annotations already mark it as readOnly and non-destructive. There is no additional behavioral detail needed or provided.

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, clear sentence with no unnecessary words or redundancy.

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

Completeness4/5

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

For a simple read tool, the description adequately conveys the primary function. It does not detail the output format, but that is likely covered by the tool's output schema, and the description is otherwise complete enough for an agent.

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?

The schema fully covers both parameters (path and force_download) with clear descriptions. The tool description adds no extra parameter context, but none is needed given the schema coverage is 100%.

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 verb ('Reads'), the resource ('Word document'), and the specific format ('.docx'). It is specific enough for an agent to understand the tool's function.

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 implies it is for reading Word documents, but does not explicitly contrast with other document-reading tools like pdf_read or ppt_read. However, the .docx qualifier provides clear scoping.

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

All local-mcp tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.