Darwin-owned Files

docx_to_text

Read-onlyIdempotent

Extract complete text from caller-supplied canonical base64 DOCX bytes using the bounded Creora document parser. Returns actual text, source/text SHA256 and ordered document parts. No URL or file lookup, network, OCR, PDF, macros, field evaluation or external writes. Refuses unsupported or over-budget documents instead of truncating. Official documentation: https://creora.darwin.so/providers/files/docs

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": {
      "documentBase64": "<documentBase64>"
    },
    "name": "docx_to_text"
  }
}

Input Schema

Name	Required	Default
`documentBase64`	Yes
`contractVersion`	No	0.1.0
`includeHeadersFooters`	No

Output Schema

Name	Required	Description	Default
`text`	Yes
`complete`	Yes
`textSha256`	Yes
`sourceParts`	No
`sourceFormat`	Yes
`sourceSha256`	Yes
`externalWrites`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 2, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Goes well beyond the annotations: discloses the bounded budget, the fail-closed policy ('refuses unsupported or over-budget documents instead of truncating'), the absence of network/OCR/macro/field evaluation, and what is returned (text, source/text SHA256, ordered parts). That is exactly the kind of non-obvious behavior an agent needs before committing to the call.

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?

Four dense sentences with the core action front-loaded, followed by scope exclusions, failure semantics, and a docs pointer. No filler and no repetition of the schema or annotations.

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?

An output schema exists, so return values need not be spelled out, and the safety profile is covered by annotations. The remaining gap is the undocumented includeHeadersFooters switch, which an agent could not discover without reading the raw schema property names.

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 carry the parameter burden, but it only implicitly covers documentBase64. The includeHeadersFooters toggle — which materially changes output — and contractVersion are never mentioned in the description or in the property definitions, leaving two of three parameters semantically undocumented.

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?

States a specific verb (extract), resource (complete text), and input form (caller-supplied canonical base64 DOCX bytes), plus the engine used (bounded Creora document parser). This clearly separates it from the format-conversion siblings such as markdown_to_pdf, xlsx_to_csv and csv_to_xlsx.

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?

Explicitly establishes the calling context (bytes must be supplied by the caller, no URL or file lookup) and enumerates what the tool will not do (network, OCR, PDF, macros, field evaluation, external writes). It does not name a sibling alternative for the cases where a URL or file path is available, so routing guidance is implied rather than complete.

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

All Darwin-owned Files 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.

Resources

Need Help?