Skip to main content
Glama

office_to_markdown

Convert Office documents (.docx, .xlsx, .pptx) to Markdown (.md) for editing, version control, or publishing.

Instructions

Convert Office document to Markdown. [Input: Office (.docx, .xlsx, .pptx) | Output: Markdown (.md)]

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>",
      "output": "<output>"
    },
    "name": "office_to_markdown"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes
outputYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior2/5

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

No annotations are supplied, so the description bears the full disclosure burden. "Convert" implies writing an output file, but it says nothing about whether output is overwritten, whether directories must exist, how conversion failures are reported, or what fidelity to expect for complex layouts.

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 compact sentences with the action front-loaded and formats in a scannable bracket notation. Nothing is wasted, though the terse bracket form leaves the path-vs-content question unaddressed.

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?

Scored against the wrong baseline placeholder

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 two bare parameters (input, output) carry no documentation anywhere. The description's "Input: Office (.docx, .xlsx, .pptx) | Output: Markdown (.md)" only implies file types and leaves the critical ambiguity unresolved: are these file paths, base64 content, or handles?

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?

The description gives a specific verb and resource ("Convert Office document to Markdown") and narrows the scope with the bracket notation listing accepted Office extensions and the .md output. It does not explicitly distinguish itself from siblings like office_extract_text or pdf_convert_markdown, so an agent must infer the boundary from format alone.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no mention of alternatives. An agent choosing between this tool, office_extract_text, and pdf_convert_markdown gets no routing help from the description.

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