@formacv/mcp

format_cv

Format candidate CVs into client-ready, ATS-safe PDF or DOCX in your agency template, inline in Bullhorn, JobAdder, or Vincere, or via MCP.

Instructions

Turn any candidate CV into a client-ready PDF or DOCX in your agency-branded template—inline inside Bullhorn, JobAdder, or Vincere, or orchestrated via MCP alongside AI agents. Mirrors FormaCV’s promise: ATS-safe typography, compliant variants for regulated clients, branded output landing back on the ATS record typically in under 60 seconds.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "cv": "<cv>",
      "template_id": "<template_id>"
    },
    "name": "format_cv"
  }
}

Input Schema

Name	Required	Description	Default
`cv`	Yes
`options`	No
`template_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 4, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Discloses behavioral traits such as ATS-safe typography, compliant variants for regulated clients, and sub-60-second completion. However, with no annotations, it lacks broader details like authentication, error behavior, or side effects on the original CV.

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 sentences with a clear initial verb ('Turn'), front-loaded with the core purpose. The phrase 'Mirrors FormaCV’s promise' adds some marketing flavor but does not significantly bloat the description.

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

Completeness3/5

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

Covers purpose and some behavioral guarantees, but with no output schema, it should clarify the return format or whether the operation is asynchronous. The description implies the CV lands on the ATS record but does not explain the direct return to the caller.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. It mentions 'template' but does not explain template_id, cv source semantics, or options like ats_safe and language. The schema alone provides minimal guidance through names/types.

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?

The description clearly states the tool's function: turning a CV into a client-ready PDF/DOCX in a branded template. It distinguishes from siblings like tailor_cv (content tailoring) and anonymize_cv by focusing on final formatted output.

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?

Provides context for where it can be used (inline in ATS or via MCP) but does not explicitly contrast with sibling tools like tailor_cv or bulk_format. The usage is implied by the tool's purpose rather than explicitly stated.

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

Deploy Server