Skip to main content
Glama
Sign In
careerproof-mcp

careerproof-mcp

by detonnate
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Add candidate profile

careerproof_add_candidate_profile

Registers a candidate's CV, extracts citable self-claims, and stores them as unverified user claims for evidence-backed interview preparation.

Instructions

Registers a candidate's CV (Markdown or plain text) and extracts individually-citable claims from it. Every extracted claim is stored with confidence 'user_claim' — it is what the candidate says about themselves, not independently verified.

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": {
      "name": "<name>",
      "cvText": "<cvText>"
    },
    "name": "careerproof_add_candidate_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesCandidate's full name
cvTextYesFull CV content in Markdown or plain text
summaryNoOptional short profile summary
headlineNoShort professional headline, e.g. 'Solutions Architect'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Adds real behavioral context beyond annotations: extracted claims are tagged with confidence 'user_claim' and are unverified assertions by the candidate, which tells the agent how to treat downstream results. Annotations only cover readOnly/idempotent/destructive hints; the semantic 'not verified' caveat is valuable. Doesn't disclose return shape or duplicate-profile behavior, so not a 5.

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

Conciseness5/5

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

Two tight sentences, front-loaded with the primary action and followed by the critical semantic caveat. No filler.

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

Completeness4/5

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

Annotation set (readOnly=false, idempotent=false, destructive=false) matches a registration tool, and the description covers the write action plus claim semantics. No output schema exists, yet the description explains the key return concept (individually-citable claims with confidence). Lacks explicit 'what happens on duplicate candidate' detail, hence not 5.

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

Parameters3/5

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

Schema description coverage is 100%, so parameters are fully documented in the schema (name, cvText, summary, headline). The description adds only format guidance ('Markdown or plain text'), which the schema already states, so baseline 3 is correct.

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?

States a specific verb ('Registers') and resource ('a candidate's CV') plus the generative action ('extracts individually-citable claims'). Far clearer than siblings like careerproof_add_project_evidence, which the description implicitly distinguishes by focusing on the candidate's own CV.

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?

Implies usage (onboarding a candidate's CV before scoring/matching), but never explicitly says when to use this vs careerproof_add_project_evidence or careerproof_index_repository, nor any prerequisites. Adequate but no alternative routing.

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

Deploy Server

Other Tools