Skip to main content
Glama

parse_document

Convert local PDFs, scans, images, DOCX, XLSX, and PPTX files into Markdown for reading or extraction, with optional page ranges and parsing modes.

Instructions

Parse a local document (PDF, image, DOCX, XLSX, PPTX ...) into Markdown.

path: file on this computer. mode: "engine" (default, most accurate) or "model-only" (one model read per
page, faster). pages: 1-based page numbers to read; all pages when omitted.

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": "parse_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoengine
pathYes
pagesNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does disclose real behavior: inputs are local files, and "model-only" costs "one model read per page" while "engine" is slower but "most accurate" — a genuine speed/accuracy cost signal. Gaps remain around file-size limits, unsupported or encrypted documents, and failure behavior.

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?

One sentence of purpose followed by a compact per-parameter breakdown; the pending decision (which mode) is stated where the agent will look for it. No filler or repeated information.

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 needn't be explained, and all three parameters are covered along with the key mode trade-off. It falls short only on edge-case behavior (unsupported formats, failures) and on routing against the sibling 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 description coverage is 0%, so the description must compensate, and it documents all three parameters: path as a local file, mode with the default plus the accuracy/speed meaning of each option, and pages as 1-based with all pages when omitted. The mode semantics add meaning well beyond the bare string enum-less schema; only the path description is thin.

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?

"Parse a local document (PDF, image, DOCX, XLSX, PPTX ...) into Markdown" names a specific verb, a resource class with concrete formats, and the output shape. It's clear what the tool does, but it never differentiates itself from the sibling extract_fields, so an agent must guess which to pick when it wants structured data.

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 context is implied by "local document" (not a URL) and by the mode trade-off, but there is no explicit when-to-use/when-not guidance and no mention of the sibling extract_fields as an alternative. The agent can infer the case for a Markdown conversion but not the boundary against extraction.

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