Rchilli Resume Parser MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_KEY | Yes | API key for authentication |
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": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| resume_parser_url_apiB | Resume Parser Url API allows you to parse resume using resume public URL. |
| resume_parser_binary_apiB | Resume Parser Binary API allows you to parse the resume using binary data in base64 format. |
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
The two tools are clearly distinct: one parses resumes from binary data in base64 format, and the other from a public URL. There is no overlap in their purposes or input methods, making it easy for an agent to choose the correct tool based on the data source available.
Both tools follow a consistent verb_noun pattern with 'resume_parser' as the prefix, followed by 'binary_api' and 'url_api' to specify the input type. This naming convention is predictable and enhances readability across the tool set.
With only two tools, the server feels thin for a resume parser domain. While it covers two common input methods (binary and URL), it lacks tools for other operations like retrieving parsed results, updating data, or handling errors, which limits its utility and scope.
The server only provides parsing tools without any complementary operations such as storing, retrieving, or managing parsed resumes. This creates significant gaps in the lifecycle of resume data, likely causing agent failures when more than basic parsing is needed.