Skip to main content
Glama

office_extract_text

Extracts plain text from Microsoft Office documents (.docx, .xlsx, .pptx) so you can reuse or process their content without manual copying.

Instructions

Extract text content from Microsoft Office documents. [Input: Office (.docx, .xlsx, .pptx) | Output: Plain Text (.txt)]

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": {
      "input": "<input>"
    },
    "name": "office_extract_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes
outputNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the transformation contract (Office in, plain text out), which implies a read-only operation, but it says nothing about whether text is returned inline or written to a file, how overwriting is handled, or failure modes.

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?

Two short clauses, front-loaded with the action and followed by a compact format contract. No filler; the bracketed notation is dense but readable, and slightly terse where prose would be clearer.

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?

For a simple two-parameter tool this covers the core contract, but with no output schema and no annotations the description should state how results are delivered (returned text vs. written .txt path) and whether the output parameter is required. That gap matters for correct 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 coverage is 0%, so the description must compensate for both parameters. The bracketed Input/Output clause does map onto the two params and constrains input to three extensions, but it does not say whether 'output' is a path, whether it is optional, or what happens if it is omitted.

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?

States a specific verb and resource (extract text from Office documents) and enumerates the accepted formats (.docx, .xlsx, .pptx). Format scoping separates it from pdf_extract_text and office_to_markdown without naming them, though an explicit contrast would be stronger.

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

Usage Guidelines3/5

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

Usage is implied only through the input-format list, so an agent can infer 'use for Office files.' There is no explicit guidance on when to prefer office_to_markdown or office_modernize_legacy, and no stated prerequisites such as handling of legacy .doc or password-protected files.

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