Skip to main content
Glama

generate_enhanced_cv

Enhance your CV by integrating recent work data from git commits, Jira tickets, and certifications with your existing resume content.

Instructions

Generate an enhanced CV by combining existing CV content with data from all sources

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
existingCvPathYesPath to existing CV (PDF or LaTeX)
sinceNoTime range for fetching recent work6 months ago

Implementation Reference

  • The primary handler function for the 'generate_enhanced_cv' tool. Parses existing CV (PDF or LaTeX), fetches recent git commits, achievements from wins.md, Jira tickets, Credly badges, and compiles a detailed report with guidelines for enhancing the CV.
    async def generate_enhanced_cv(existing_cv_path: Optional[str], since: str) -> list[TextContent]:
        """Generate enhanced CV combining all data sources."""
        if not existing_cv_path:
            return [TextContent(type="text", text="Error: existingCvPath parameter is required")]
        
        # Resolve path
        if existing_cv_path.startswith('/'):
            resolved_path = Path(existing_cv_path)
        else:
            resolved_path = Path(REPO_PATH) / existing_cv_path
        
        if not resolved_path.exists():
            return [TextContent(type="text", text=f"CV file not found: {resolved_path}")]
        
        try:
            # Step 1: Parse existing CV
            if resolved_path.suffix.lower() == '.pdf':
                reader = pypdf.PdfReader(str(resolved_path))
                existing_content = ""
                for page in reader.pages:
                    existing_content += page.extract_text() + "\n"
            else:
                existing_content = resolved_path.read_text()
            
            # Step 2: Gather all data sources
            data_sections = []
            
            # Git commits
            git_result = await get_git_log(since)
            data_sections.append(f"\n## Git Commits ({since}):\n{git_result[0].text}")
            
            # Wins
            wins_result = await read_wins()
            data_sections.append(f"\n## Achievements (wins.md):\n{wins_result[0].text}")
            
            # Jira tickets
            if all([JIRA_URL, JIRA_EMAIL, JIRA_API_TOKEN]):
                jira_result = await get_jira_tickets(since, "Done")
                data_sections.append(f"\n{jira_result[0].text}")
            else:
                data_sections.append("\n## Jira Tickets: Not configured")
            
            # Credly badges
            if CREDLY_USER_ID:
                credly_result = await get_credly_badges(50)
                data_sections.append(f"\n{credly_result[0].text}")
            else:
                data_sections.append("\n## Credly Badges: Not configured")
            
            # LinkedIn
            if LINKEDIN_PROFILE_URL:
                data_sections.append(f"\n## LinkedIn Profile: {LINKEDIN_PROFILE_URL}\n(Manual review recommended)")
            
            # Step 3: Compile report
            truncated_cv = existing_content[:2000]
            if len(existing_content) > 2000:
                truncated_cv += "\n... (truncated, full content available)"
            
            report = f"""# Enhanced CV Generation Report
    
    ## Existing CV Content:
    {truncated_cv}
    
    ## Recent Work & Achievements ({since}):
    {''.join(data_sections)}
    
    ---
    
    ## CV Guidelines:
    - Maximum {MAX_BULLETS_PER_EXPERIENCE} bullet points per experience
    - Focus on quantifiable impact and results
    - Use action verbs (Engineered, Designed, Implemented, Led, etc.)
    - Include metrics (percentages, time savings, scale)
    
    ## Next Steps:
    1. Review the existing CV content above
    2. Analyze the recent work data (git commits, Jira tickets, badges)
    3. Identify the top {MAX_BULLETS_PER_EXPERIENCE} most impactful achievements
    4. Generate enhanced CV bullet points in LaTeX format
    5. Ensure each bullet demonstrates clear business value
    
    ## Suggested Approach:
    Ask the AI to:
    "Based on the above data, generate {MAX_BULLETS_PER_EXPERIENCE} enhanced CV bullet points in LaTeX format that highlight my most significant recent achievements with quantifiable results."
    """
            
            return [TextContent(type="text", text=report)]
        
        except Exception as e:
            return [TextContent(type="text", text=f"Enhanced CV generation error: {str(e)}")]
  • Registration of the 'generate_enhanced_cv' tool in the list_tools() handler, defining its name, description, and input schema.
    Tool(
        name="generate_enhanced_cv",
        description="Generate an enhanced CV by combining existing CV content with data from all sources",
        inputSchema={
            "type": "object",
            "properties": {
                "existingCvPath": {
                    "type": "string",
                    "description": "Path to existing CV (PDF or LaTeX)"
                },
                "since": {
                    "type": "string",
                    "description": "Time range for fetching recent work",
                    "default": "6 months ago"
                }
            },
            "required": ["existingCvPath"]
        }
    )
  • Input schema definition for the 'generate_enhanced_cv' tool, specifying parameters existingCvPath (required) and since (optional, default '6 months ago').
    inputSchema={
        "type": "object",
        "properties": {
            "existingCvPath": {
                "type": "string",
                "description": "Path to existing CV (PDF or LaTeX)"
            },
            "since": {
                "type": "string",
                "description": "Time range for fetching recent work",
                "default": "6 months ago"
            }
        },
        "required": ["existingCvPath"]
    }
  • Dispatch logic in the general call_tool handler that routes calls to the specific generate_enhanced_cv function.
    elif name == "generate_enhanced_cv":
        return await generate_enhanced_cv(
            arguments.get("existingCvPath"),
            arguments.get("since", "6 months ago")
        )
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool generates an enhanced CV but does not clarify key behaviors: whether this is a read-only or mutation operation (e.g., does it modify the original CV?), what 'enhanced' entails (e.g., formatting, content addition), potential side effects, or output format. For a tool with no annotation coverage, this lack of detail is a significant gap in transparency.

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?

The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It is front-loaded and avoids redundancy, making it easy to parse. However, it could be slightly more structured by hinting at the outcome or process, but overall, it earns its place with clear communication.

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

Completeness2/5

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

Given the complexity of generating an enhanced CV with multiple data sources, the description is incomplete. No annotations are provided to clarify safety or behavior, and there is no output schema to explain the result format. The description lacks details on what 'enhanced' means, how data is combined, or any error conditions. For a tool with no structured support and potential for varied outputs, this leaves significant gaps for an agent to understand its full context.

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?

The input schema has 100% description coverage, with clear documentation for both parameters ('existingCvPath' and 'since'). The description adds minimal value beyond the schema, as it does not explain parameter interactions, provide examples, or clarify semantics like what 'data from all sources' means in relation to the 'since' parameter. Given the high schema coverage, a baseline score of 3 is appropriate, as the description does not compensate with additional insights.

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

Purpose4/5

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

The description clearly states the tool's purpose: 'Generate an enhanced CV by combining existing CV content with data from all sources.' It specifies the verb ('generate'), resource ('enhanced CV'), and scope ('combining existing CV content with data from all sources'), which is specific and actionable. However, it does not explicitly differentiate from sibling tools like 'parse_cv_pdf' or 'read_cv', which might handle CV data extraction or reading, leaving some ambiguity about its unique role.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It mentions 'data from all sources' but does not specify what those sources are or how this differs from tools like 'get_linkedin_profile', 'get_credly_badges', or 'analyze_commits_impact', which might provide specific data types. There is no indication of prerequisites, exclusions, or optimal contexts for use, leaving the agent to infer usage based on the name alone.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/eyaab/cv-resume-builder-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server