Retrieve all text from a DOCX document by providing its docId, enabling programmatic text extraction for further processing.
Get all text from document
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "docx.get_text"
}
}| Name | Required | Description | Default |
|---|---|---|---|
| docId | No |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so the description carries the full burden. It only states a high-level operation and does not disclose what 'all text' includes (tables, footnotes, comments), the return format, or side effects. It implies reading but lacks behavioral detail.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single concise sentence with zero fluff. It is front-loaded and every word contributes to the meaning.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no annotations and no output schema, the description should explain the return value and any constraints. It only says 'Get all text' without indicating output type, scope, or document state requirements, leaving an agent under-informed.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has one parameter, docId, with no description and no schema coverage. The tool description does not mention the parameter or clarify how to provide the document ID, leaving the bare name as the only semantic hint.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('Get') and resource ('all text from document'), making the tool's purpose clear. It is distinct from sibling tools like docx.part_read and docx.find, though it does not explicitly name alternatives or scope (e.g., whether headers/footers are included).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No usage guidance is provided. The description does not state when to prefer get_text over part_read or find, nor does it mention prerequisites such as opening the document via docx.open.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.