MCP Job Matching 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
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_mock_jobsA | Retrieve list of mock job postings including requirements and metadata. |
| calculate_match_scoreA | Calculate a detailed match score between a candidate's skills and a job description. |
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 have clearly distinct purposes: one calculates a match score, the other retrieves mock job postings. No overlap or ambiguity.
Both tools follow a consistent verb_noun pattern with underscores, making the naming predictable and clear.
With only 2 tools, the server feels minimal. While it may cover a narrow scope, typical job matching servers would require more tools, so the count is borderline.
The tool set is severely incomplete for a job matching domain. It lacks essential operations like searching jobs, managing candidate profiles, or submitting applications, leaving agents with limited functionality.