Skip to main content
Glama
Sign In
OpenDocKit

OpenDocKit

by hyeonsang010716
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

convert_document

Read-onlyIdempotent

Reads local PDF, Word, PowerPoint, Excel, CSV, HTML, EPUB and email files as Markdown, keeping table rows and columns, with optional page, slide or sheet ranges.

Instructions

Convert a local document to Markdown.

path: the file to read (absolute, or relative to where the server was started). sections: which pages, slides or sheets to return, by their numbers in document_outline: "3" or "2-5". Leave out for the whole document. max_chars: the most characters of the document to return (default 100,000). A longer text is cut there, and a note after it says so.

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": {
      "path": "<path>"
    },
    "name": "convert_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
sectionsNo
max_charsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.2

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, closed-world semantics, so the bar is lower. The description adds real value beyond them: truncation at max_chars with a note appended, the default of 100,000, and that relative paths resolve against the server's start directory.

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?

A front-loaded one-line purpose followed by one line per parameter, each covering exactly one concern. No redundant or filler sentences.

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?

For a three-parameter conversion tool with no output schema and strong annotations, this covers the essentials an agent needs to call it correctly, including truncation. Minor gaps remain around error behavior and how non-text elements or unsupported formats are handled.

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

Parameters5/5

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

Schema coverage is 0%, so the description must carry the parameters and it does: path resolution rules, the accepted sections syntax ("3" or "2-5") and its dependency on document_outline, and max_chars with its default and truncation behavior. All three parameters gain meaning not present in the bare schema types.

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 ("Convert a local document to Markdown"), which is unambiguous and clearly distinct from the outline sibling. It stops short of explicitly contrasting itself with document_outline as a tool choice, leaving that only implicit in the parameter text.

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?

The sections parameter tells the agent the numbers come from document_outline, which implicitly establishes a get-outline-then-convert workflow, and "Leave out for the whole document" gives the default path. There is no explicit statement about when to prefer this tool over the sibling or what document types are unsupported.

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

Deploy Server

Other Tools