document-parser git:20260813.48597a3A

Immutable. This exact content is served forever at /api/v1/blob/2ee9da6cb827efbd.

---
name: document-parser
description: "Parse and extract structured content from PDFs, Word documents, and other file formats. Converts documents into clean, machine-readable text for analysis, summarization, data extraction, and content processing workflows."
---

# Document Parser

Parse and extract structured content from PDFs, Word documents, and other file formats. Converts documents into clean, machine-readable text for analysis, summarization, data extraction, and content processing workflows. Read [the API map](references/sandbase-api-map.md) before selecting a capability.

## Call SandBase capabilities

For every selected tool, call `sandbase_describe_tool` first and use only arguments in its current input schema. Then call `sandbase_call_tool` with the exact `tool_name`.

## Available Tools

- `agentbody_document_parse`

## Workflow

1. Understand the user's research question, target, and context.
2. Call `sandbase_describe_tool` for each selected tool to confirm parameter schema.
3. Call `sandbase_call_tool` with the exact tool_name and schema-defined arguments.
4. Synthesize findings into a clear, evidence-backed answer.
5. Cite sources, note evidence gaps, and separate observations from interpretations.

## Guidelines

- Always call `sandbase_describe_tool` before using any capability.
- Cite sources and preserve attribution (URLs, usernames, dates, metrics).
- Separate factual observations from analysis and recommendations.
- If data is unavailable, note the gap and continue with available evidence.
- Read-only research only. Never take actions on platforms.