Skip to main content
Glama

delete_resume

Remove a LaTeX resume file from the LaTeX Resume MCP server to manage storage and maintain organized resume collections.

Instructions

Delete a LaTeX resume file.

Args:
    filename: Name of the resume file to delete

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filenameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The delete_resume tool handler function, registered via @mcp.tool() decorator. It deletes the specified LaTeX resume file (.tex) from the resumes directory after ensuring directories exist and filename has .tex extension. Returns JSON success or error message.
    @mcp.tool()
    def delete_resume(filename: str) -> str:
        """
        Delete a LaTeX resume file.
    
        Args:
            filename: Name of the resume file to delete
        """
        ensure_dirs()
        filepath = get_resumes_dir() / ensure_tex_extension(filename)
    
        if not filepath.exists():
            return json.dumps({"error": f"Resume '{filename}' not found"})
    
        try:
            filepath.unlink()
            return json.dumps({"success": True, "deleted": str(filepath)})
        except Exception as e:
            return json.dumps({"error": f"Error deleting file: {str(e)}"})
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 deletes a file, implying a destructive mutation, but doesn't specify if deletion is permanent, requires confirmation, affects other data, or has permission requirements. This is a significant gap for a destructive operation with zero annotation coverage.

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 extremely concise and well-structured: a clear purpose statement followed by a brief parameter explanation. Every sentence earns its place, with no redundant or vague language, making it easy 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 destructive nature, no annotations, and an output schema (which might cover return values), the description is minimally adequate. It states what the tool does and the parameter, but lacks critical behavioral details like safety warnings or error handling. The presence of an output schema prevents a lower score, but more context is needed for a destructive operation.

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 description adds meaningful context for the single parameter 'filename' by specifying it as 'Name of the resume file to delete', which clarifies its role beyond the schema's basic title 'Filename'. With 0% schema description coverage and only one parameter, this compensates adequately, though it doesn't detail format constraints (e.g., file extensions).

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 ('Delete') and resource ('a LaTeX resume file'), making the purpose immediately understandable. It distinguishes itself from siblings like 'create_resume', 'edit_resume', and 'read_resume' by specifying deletion. However, it doesn't explicitly contrast with 'list_resumes' or other file operations, keeping it from a perfect 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. It doesn't mention prerequisites (e.g., the file must exist), exclusions (e.g., cannot delete non-existent files), or related tools like 'list_resumes' for checking available files. This lack of context leaves the agent to infer usage scenarios.

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/dannywillowliu-uchi/resume_mcp'

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