Job Application Agent MCP Server

read_cv

Read-only

Retrieves your CV's profile, languages, skills, and citable facts with unique IDs, enabling agents to ground job application claims in verified data.

Instructions

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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "read_cv"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 2, 2026

TDQS

A4.2/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds information the annotations do not: the fact-ID scheme (p1.f2, e1, ed1, lang1, av) and the distinction between verified skills (used in a project or job) and unverified ones (only listed). That is real semantic context for interpreting the payload.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact blocks: what it returns first, then how to decode the IDs and verification flag. Every sentence earns its place and nothing is padded. Minor deduction because the ID-scheme parenthetical is dense and wrapped awkwardly rather than structured as a short list.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present the description need not explain return structure, and with zero parameters there is no argument guidance needed. It covers content scope, ID semantics and the verified/unverified flag, which is everything an agent needs to call and interpret this tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters and schema coverage is 100%, which is the baseline-4 case. There is nothing parameter-wise for the description to compensate for, and it correctly spends no space on arguments.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

It states a specific verb ('Read') and resource ('the user's CV') and then enumerates the exact content returned: profile, languages, skills and citable facts. No sibling (search_jobs, score_match, draft_cover_letter, request_approval) does anything similar, so an agent can route instantly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies read usage through the verb but never states when to call this rather than the sibling tools, nor any prerequisites. With zero parameters and readOnlyHint=true, the usage is largely self-evident, but there is no explicit guidance or exclusion.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server