Tools reference

Complete reference of every tool the GroupDocs.Viewer MCP server exposes to AI agents, with parameters, example prompts, and results. Captured from a live tools/list call against server version 26.9.0 (raw capture: tools-list.generated.json in this section’s source).

ToolWhat it does
render_pageRenders one document page as a PNG image, returned inline and saved to storage
get_view_infoReturns file type, page count, and per-page dimensions without rendering
get_license_statusReports the active licensing mode and, under metered licensing, consumption

The FileInput shape

Every tool takes its document through the same file object — pass either a name from your storage folder or inline content:

{ "file": { "filePath": "report.pdf" } }
FieldTypeDescription
filePathstringFile path or name in the configured storage folder
fileContentstringBase64-encoded file content (alternative to filePath)
fileNamestringOriginal filename with extension — required with fileContent. Since 26.9.0 it also works on its own, resolved from the storage folder exactly like filePath

You rarely write this JSON yourself: the AI agent does, from your plain-language prompt. Missing files are not an error to fear — the tool responds with the list of available files so the agent can correct itself.