Skip to main content
Glama

read_cv

Read and display your current LaTeX-formatted CV/resume content for review and editing within the CV Resume Builder MCP server.

Instructions

Read current CV (LaTeX)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that reads the cv.tex file from REPO_PATH and returns its content as TextContent. Handles case where file does not exist.
    async def read_cv() -> list[TextContent]:
        """Read the current CV file."""
        cv_path = Path(REPO_PATH) / "cv.tex"
        
        if not cv_path.exists():
            return [TextContent(type="text", text="CV file not found")]
        
        content = cv_path.read_text()
        return [TextContent(type="text", text=f"Current CV:\n\n{content}")]
  • Tool registration in list_tools(), defining name, description, and empty input schema.
    Tool(
        name="read_cv",
        description="Read current CV (LaTeX)",
        inputSchema={
            "type": "object",
            "properties": {}
        }
    ),
  • Dispatch in call_tool() that invokes the read_cv handler when the tool name matches.
    elif name == "read_cv":
        return await read_cv()
  • Input schema definition for the read_cv tool (empty properties, no required inputs).
    inputSchema={
        "type": "object",
        "properties": {}
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool reads a CV, implying a read-only operation, but doesn't specify what 'current' means (e.g., file path, default location), potential errors, or output format. This leaves significant gaps in understanding how the tool behaves.

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?

The description is a single, efficient sentence with zero waste—it directly states the tool's purpose without fluff. It's appropriately sized and front-loaded, making it easy for an agent to parse quickly.

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?

Given the tool's simplicity (0 parameters, no annotations, no output schema), the description is adequate as a minimum viable explanation. However, it lacks details on what 'current' entails or the output format, which could be important for an agent to use it correctly without trial and error.

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 has 0 parameters, and schema description coverage is 100%, so there's no need for parameter details in the description. The baseline for 0 parameters is 4, as the description appropriately doesn't add unnecessary information beyond confirming the lack of inputs.

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 action ('Read') and the resource ('current CV (LaTeX)'), making the purpose immediately understandable. However, it doesn't distinguish this tool from sibling tools like 'parse_cv_pdf' or 'get_cv_guidelines', which might also involve CV operations, so it doesn't reach the highest score.

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 like 'parse_cv_pdf' or 'generate_enhanced_cv'. It lacks explicit context, prerequisites, or exclusions, leaving the agent to infer usage from 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