Skip to main content
Glama
Job Application Agent MCP Server

Job Application Agent MCP Server

by Kirill-ark

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CV_PATHNoPath to the CV file served by the MCP server. Defaults to the example CV.
GROQ_API_KEYYesGroq API key used by the LLM for tools such as drafting cover letters. Create one at console.groq.com/keys and put it in GROQ_API_KEY.

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_jobsA

Search current job vacancies in Germany (Arbeitnow job board).

    Args:
        query: What the job is about, e.g. "machine learning" or "data engineer".
            Do not put seniority or city here.
        location: City, e.g. "Berlin". Remote jobs match any location.
        level: Ranks this seniority higher: student, intern, entry or experienced.
        limit: Maximum number of results, 1-20.

    Returns short vacancies, best first. Use their `id` with score_match.
    
read_cvA

Read the user's CV: profile, languages, skills and citable facts.

    Every fact has an ID (p1.f2 = project 1, fact 2; e1 = job 1; ed1 =
    education; lang1 = language; av = availability). Verified skills were
    used in a project or job; unverified ones are only listed.
    
score_matchA

Score how well one vacancy fits the CV, from 0 to 100.

    Args:
        job_id: The `id` of a vacancy returned by search_jobs.

    Returns the score, a label (good >= 65, maybe >= 30, bad), matched
    skills, gaps and a short explanation. Results are cached.
    
draft_cover_letterA

Write a cover letter draft for one vacancy, using only facts from the CV.

    Args:
        job_id: The `id` of a vacancy returned by search_jobs. Score it first.

    Every sentence is checked against the CV. `grounded` is false when
    problems are left; they are listed in `issues` for the user. The draft
    is saved and put into the user's approval queue (mark_ready), never
    sent. Each call makes a new draft, so call it once per vacancy.
    
request_approvalA

Ask the user to approve an action on a draft. You cannot approve it yourself.

    Args:
        action: "mark_ready" (the letter is final; drafts are already queued for
            this) or "export" (give the user the text; only after mark_ready was
            approved). Sending, emailing or applying is never possible and will
            be refused.
        draft_id: The `draft_id` returned by draft_cover_letter.

    The request waits for the user's decision in the UI. Do not ask again
    and do not wait for it: finish your answer and tell the user.
    

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.4/5.0

Scored across 5 tools

Disambiguation5/5

Each tool occupies a distinct stage of a linear pipeline: search_jobs (discover vacancies), read_cv (load candidate facts), score_match (evaluate one vacancy), draft_cover_letter (produce a grounded draft), and request_approval (gate an action). Descriptions reinforce the boundaries, e.g. score_match requires a job_id from search_jobs and draft_cover_letter says to score first, so an agent cannot easily pick the wrong one.

Naming Consistency5/5

All five names are snake_case verb_noun pairs (search_jobs, read_cv, score_match, draft_cover_letter, request_approval). The verb accurately reflects each tool's action, and there is no mixing of conventions or casing styles.

Tool Count5/5

Five tools map exactly to the five steps of the stated purpose (find job, read CV, score, draft, approve), with no redundant or speculative extras. This is a well-scoped, minimal surface for a single-agent workflow.

Completeness4/5

The end-to-end lifecycle (search → CV → score → draft → approval/export) is fully covered, including a deliberate safety boundary on sending. Minor gaps remain: there is no way to list or retrieve previously saved drafts, and no way to revise a draft (each call creates a new one), so agents must work around those limits.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues