Skip to main content
Glama
ExaDev

document-mcp

by ExaDev
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

Inspect PDF

pdf_inspect

Parse a PDF to inspect its structure: get page count, per-page sizes and item histograms, metadata, and embedded image formats. Optionally return the full parsed layout.

Instructions

Parses a PDF (documents.js's readPdf) and reports a summary: page count, each page's own size and item-kind histogram, document metadata, and embedded image formats. Pass full: true to return the entire parsed LayoutDocument instead of a summary.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fullNoWhen true, return the entire parsed LayoutDocument instead of a summary. Defaults to false.
sourceYesThe PDF document to inspect.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changedv2.1.8
    • changedInput schema / properties / source / anyOf
      Previous value: -[
-  {
-    "properties": {
-      "path": {
-        "description": "Filesystem path to the document to read. The document format is inferred from the file extension.",
-        "type": "string"
-      }
-    },
-    "required": [
-      "path"
-    ],
-    "type": "object"
-  },
-  {
-    "properties": {
-      "bytesBase64": {
-        "description": "Base64-encoded document bytes.",
-        "type": "string"
-      },
-      "format": {
-        "description": "The document format of bytesBase64 -- required, since inline bytes carry no filename to infer it from.",
-        "enum": [
-          "docx",
-          "pptx",
-          "xlsx",
-          "odt",
-          "odp",
-          "ods",
-          "odg",
-          "odf",
-          "markdown",
-          "pdf"
-        ],
-        "type": "string"
-      }
-    },
-    "required": [
-      "bytesBase64",
-      "format"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "properties": {
+      "path": {
+        "description": "Filesystem path to the document to read. The document format is inferred from the file extension.",
+        "type": "string"
+      }
+    },
+    "required": [
+      "path"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "bytesBase64": {
+        "description": "Base64-encoded document bytes.",
+        "type": "string"
+      },
+      "format": {
+        "description": "The document format of bytesBase64 -- required, since inline bytes carry no filename to infer it from.",
+        "enum": [
+          "docx",
+          "pptx",
+          "xlsx",
+          "odt",
+          "odp",
+          "ods",
+          "odg",
+          "svg",
+          "odf",
+          "csv",
+          "markdown",
+          "pdf"
+        ],
+        "type": "string"
+      }
+    },
+    "required": [
+      "bytesBase64",
+      "format"
+    ],
+    "type": "object"
+  }
+]
  2. Addedv1.1.6

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the burden of behavioral disclosure. It explains the output (summary vs full LayoutDocument) but does not mention side effects, permissions, or error behavior. As a read-only parse operation, side effects are minimal, but the description does not explicitly confirm safety or limitations.

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?

The description is two sentences, front-loaded with the core outcome, and every word adds value. No redundant information or filler.

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?

Given the tool's simplicity (2 parameters, no output schema), the description adequately explains what the tool returns and how to get full results. It lacks discussion of error cases or performance limitations, but for a parsing tool with clear schema, this is nearly complete.

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%, and the description adds value by clarifying the 'full' parameter's effect (return entire LayoutDocument instead of summary). The 'source' parameter is adequately described in the schema, and the description reinforces it. This exceeds the baseline for high-coverage schemas.

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?

The description clearly states the tool parses a PDF and reports a summary with specific components (page count, page sizes, item-kind histogram, metadata, image formats). It also distinguishes from sibling tools by focusing on inspection rather than conversion or manipulation.

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?

The usage context is implied: use this to inspect a PDF and get a summary. However, there is no explicit guidance on when to use it versus alternatives like convert_document or metadata_read. The description focuses on the full parameter but does not address when to choose this tool over others.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ExaDev/document-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server