extract

Parse Document

parse_document

Idempotent

Parse a quoted PDF to structured Markdown (hallucination-guarded OCR for scanned pages, Japanese-strong). Get quote_id from quote_parse first; price is fixed by the quote.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`quote_id`	Yes	quote_id returned by quote_parse (price is fixed by the quote)
`x_payment`	No	Optional: base64 X-PAYMENT header value (x402 exact scheme, USDC on Base mainnet). Omit it to receive the payment requirements (accepts[] + docs) for this call without being charged.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 27, 2026
- addedInput schema / properties / quote_id / description
```
Added value: +"quote_id returned by quote_parse (price is fixed by the quote)"
```

Changed4 schema fields changedJul 31, 2026

addedInput schema / properties / quote_id
```
Added value: +{
+  "type": "string"
+}
```

removedInput schema / properties / url

Removed value: -{
-  "type": "string"
-}

addedInput schema / properties / x_payment

Added value: +{
+  "description": "Optional: base64 X-PAYMENT header value (x402 exact scheme, USDC on Base mainnet). Omit it to receive the payment requirements (accepts[] + docs) for this call without being charged.",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "url"
-]New value: +[
+  "quote_id"
+]

AddedJul 20, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Beyond annotations, the description adds valuable behavioral context: 'hallucination-guarded OCR for scanned pages, Japanese-strong' and the fact that the price is fixed. It does not contradict annotations (readOnlyHint=false, idempotentHint=true) and aligns with the paid nature implied by the x_payment parameter.

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?

Two sentences with no waste. The primary purpose is front-loaded, followed by a necessary prerequisite and a cost note. Every phrase earns its place.

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 tool with 2 parameters, no output schema, and clear annotations, the description covers the essential aspects: what it does, the prerequisite, and the OCR specifics. It does not describe return structure in detail, but 'structured Markdown' gives a sufficient idea. It lacks explicit alternative routing, but that is not critical given the context.

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?

Schema description coverage is 100% and the description does not add new meaning beyond the schema. It repeats the quote_id origin and price fixed, but does not elaborate on x_payment behavior beyond what the schema already states. Baseline 3 is appropriate.

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 action ('Parse a quoted PDF to structured Markdown') with a specific resource and output format. It also distinguishes the tool by mentioning OCR capabilities and language support, which differentiates it from siblings like pdf_info or structured_extract.

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 description provides a clear prerequisite ('Get quote_id from quote_parse first') and a key behavioral condition ('price is fixed by the quote'). It does not explicitly name alternatives or exclusions, but the context is sufficient for an agent to know when to use it.

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

All extract tools Inspect

Try in Browser

Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?