Nutrient PDF MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_pdf_object_treeB | Nutrient PDF MCP Server - Get JSON representation of PDF object tree with lazy loading |
| resolve_indirect_objectC | Nutrient PDF MCP Server - Resolve a specific indirect object by its ID |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
Each tool has a clearly distinct purpose: one retrieves the entire object tree structure, the other resolves a specific indirect object by ID. There is no overlap or ambiguity between them.
Both tools follow a consistent verb_noun pattern with underscore: 'get_pdf_object_tree' and 'resolve_indirect_object'. The naming is uniform and predictable.
With only 2 tools, the surface is minimal but appropriate for the narrow domain of PDF object tree inspection. It's borderline, but each tool serves a specific, complementary purpose.
For the stated purpose of exploring a PDF object tree, the tools provide tree retrieval and resolution of indirect objects. However, missing operations like filtering objects by type or searching objects limit completeness for more advanced use cases.