302AI File Parser MCP Server
Server 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| parseFileToTextC | Provide a file url, parse the file to text, return the text as a string. |
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
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly distinct as it is the sole operation available.
The single tool name follows a clear verb_noun pattern (parseFileToText), and with only one tool, consistency is inherently perfect as there are no other names to compare against.
A single tool is generally too few for a server named 'File Parser', as this suggests a domain that might include operations like parsing different file types, handling errors, or extracting metadata. The scope feels incomplete with just one basic parsing function.
The server's name implies a broader file parsing capability, but the tool set only includes parsing files to text. Obvious gaps include support for different file formats (e.g., PDF, DOCX), structured data extraction, or error handling, making the surface severely incomplete for the apparent purpose.