Skip to main content
Glama

pdf-suite

pdf_to_markdown

Extract uncompressed PDF text operators (Tj/TJ) and document metadata into clean Markdown.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "pdf_to_markdown"
  }
}

Input Schema

NameRequiredDescriptionDefault
filePathNo
base64DataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden. Mentioning Tj/TJ operators and 'uncompressed' text is a useful hint that compressed streams or scanned/image PDFs likely yield nothing, but the description says nothing about error behavior, fidelity limits, or output structure.

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 front-loaded sentence with no filler; the operator terminology earns its place by signalling an extraction constraint. It is compact but perhaps too compact given the undocumented inputs.

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

Completeness2/5

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

With zero annotation coverage, zero parameter documentation, and no output schema, the description needs to do much more. It omits how to supply the PDF (path vs base64), whether one is required, and what the returned Markdown looks like.

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 description must explain filePath and base64Data. It says nothing about them, leaving the critical question of whether these are two alternative input modes (mutually exclusive) entirely undocumented.

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: extract PDF text operators and metadata into Markdown. The transform direction (PDF -> Markdown) is unambiguous and clearly distinct from the sibling manipulation tools like pdf_merge or pdf_rotate, though it never explicitly names an alternative.

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 routing to alternatives. The word 'uncompressed' hints at a limitation but the description never states when this tool will fail or when another approach is needed.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources