Skip to main content
Glama

Import a Word document

import_word_document
Read-onlyIdempotent

Convert a Word document (.docx, or best-effort .doc) into md2sign markdown. Keeps headings, bold and italics, numbered and bulleted lists, tables and links; images are dropped. Nothing is saved: review the returned markdown, add a [[signature: Name ]] field for each person who needs to sign (see signing_advice), then call create_draft. Returns markdown, title, import_warnings and validation. Max 10 MB.

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": {
      "content_base64": "<content_base64>"
    },
    "name": "import_word_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
api_keyNoAn md2sign API key. When given, this call uses that key's account even if the connection is signed in as someone else, so pass it on every call when your human has more than one md2sign account (for example two businesses). Also use it if your MCP client cannot send an "Authorization: Bearer <api_key>" header.
filenameNoOriginal file name, e.g. "Services Agreement.docx". Optional.
content_base64YesThe file's bytes, base64-encoded (a data: URL prefix is accepted).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / api_key / description
      Previous value: -"Your md2sign API key. Only needed if your MCP client cannot send an \"Authorization: Bearer <api_key>\" header."New value: +"An md2sign API key. When given, this call uses that key's account even if the connection is signed in as someone else, so pass it on every call when your human has more than one md2sign account (for example two businesses). Also use it if your MCP client cannot send an \"Authorization: Bearer <api_key>\" header."
  2. Added

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, non-destructive), the description discloses lossy conversion behavior (images dropped), that no state is persisted, best-effort .doc support, and a hard 10 MB size ceiling — exactly the operational facts an agent needs before uploading a file.

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?

Front-loaded with the conversion statement, then fidelity, then the workflow, then return values and the size limit. Every clause carries distinct information; there is no restatement of the tool name or filler.

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

Completeness5/5

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

With no output schema, the description names the return fields (markdown, title, import_warnings, validation) so the agent knows what to inspect. Combined with the pipeline guidance and size limit, nothing material is missing for a three-parameter conversion tool.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds constraints the schema does not: accepted input formats (.docx, best-effort .doc) for content_base64 and a 10 MB maximum size. It adds nothing about filename or api_key, which the schema already covers adequately.

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?

"Convert a Word document (.docx, or best-effort .doc) into md2sign markdown" is a specific verb plus resource plus output format. It enumerates what is preserved (headings, bold/italics, lists, tables, links) and what is not (images), so an agent can distinguish it from create_draft, render_preview, or validate_markdown without opening a schema.

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?

It states an explicit post-condition ("Nothing is saved") and a concrete next step in the pipeline: review the markdown, insert [[signature: Name <email>]] fields per signer, then call create_draft, with a pointer to signing_advice. It does not explicitly say when to prefer create_document_from_template or another import path, so the alternative-selection side is only implied.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.