​

get_document_full_content

​

Use Cases

• Read the full content of an uploaded document
• Export or process document text in your application
• Get complete text when search snippets are insufficient
• Build document viewers or full-text interfaces

​

Parameters

​

Response (success)

​

Response (not found)

​

Example Request

{
  "document_name": "Product Guide.pdf"
}

​

Example Response (success)

{
  "success": true,
  "document": "Product Guide.pdf",
  "chunk_count": 5,
  "full_text": "Introduction\n\nThis guide covers...\n\nChapter 1\n\n..."
}

​

Example Response (not found)

{
  "success": false,
  "error": "Document 'Unknown.pdf' not found in granted knowledge sources.",
  "available": ["Product Guide.pdf", "API Documentation"]
}

​

Behavior

• Partial matching: Pass a substring of the document name (e.g. “Product” for “Product Guide.pdf”); matching is case-insensitive
• Full text: Returns all chunks in order, concatenated — unlike search_knowledge, which returns only relevant excerpts
• Scoping: MCP can access all project documents; no agent filtering

​

Error Handling

​

Best Practices

1. Get names from list: Call list_knowledge_documents first to get exact or display names
2. Use partial names: You can pass “Product” instead of “Product Guide.pdf” if it uniquely matches
3. Handle large text: Full document content can be large; stream or paginate in your UI if needed

​

Related Tools

• list_knowledge_documents: List document names to pass here
• search_knowledge: Semantic search over knowledge (returns excerpts, not full text)