NetMind ParsePro
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NETMIND_API_TOKEN | Yes | Your Netmind API key. You can obtain an API key from https://www.netmind.ai/user/apiToken |
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| parse_pdfA | |
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 1 tool
Only one tool exists, so there is no possibility of confusion between tools. The tool's purpose is clearly defined.
The tool name 'parse_pdf' follows a clear verb_noun pattern, which is consistent. Since it's the only tool, the naming is perfectly consistent.
With only one tool, the server is minimal. While it serves a focused purpose (PDF parsing), a single tool feels thin compared to typical servers that offer multiple operations. It is borderline appropriate.
The tool covers the essential functionality of parsing a PDF and returning content in two common formats. For a dedicated PDF parser, this is complete. No obvious missing features like page range filtering or OCR are required for basic usage.