Skip to main content
Glama
Sign In
mcp-docparser

mcp-docparser

by Jasonzld
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get_document_info

Extract metadata and structure from documents or images by passing a file path; supports PDF, Word, Excel, and OCR images.

Instructions

Get metadata and structure information about any document or image

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": {
      "file_path": "<file_path>"
    },
    "name": "get_document_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_pathYesPath to the document or image file

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It says nothing about whether the file is read or mutated, what permissions are needed, cost/latency, or whether it works on unsupported formats despite claiming 'any document or image'.

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?

A single efficient sentence with the resource and scope front-loaded. Nothing is wasted, though the terseness is part of the under-specification problem.

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

Completeness3/5

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

For a lightweight read-only info tool with no output schema, the description should at least sketch what 'metadata and structure' contains. It is callable as written but leaves the return shape entirely opaque.

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

Parameters3/5

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

Only one parameter, and the schema already documents it at 100% coverage ('Path to the document or image file'). The description adds no format, path-resolution, or size-limit detail beyond the schema, so the baseline 3 applies.

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?

Specific verb (Get) plus resource (metadata and structure information) scoped to documents and images. It implicitly separates itself from extract_text/ocr_image by promising metadata/structure rather than content, but it never names or contrasts those siblings explicitly.

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 and no exclusions. With siblings like parse_document, extract_text, and analyze_image, an agent must guess whether this is a precursor step, an alternative, or orthogonal.

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