Skip to main content
Glama
dannywillowliu-uchi

LaTeX Resume MCP

by dannywillowliu-uchi
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

get_config

Retrieve current configuration settings, including directory paths and pdflatex status, for managing LaTeX resume files.

Instructions

Get current configuration including directories and pdflatex status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • src/latex_resume_mcp/server.py:566-582 (handler)
    The main handler function for the 'get_config' tool. Decorated with @mcp.tool(), it returns a JSON string containing the resumes and templates directories, pdflatex installation status and path, and environment variable information.
    @mcp.tool()
def get_config() -> str:
    """
    Get current configuration including directories and pdflatex status.
    """
    pdflatex = find_pdflatex()
    return json.dumps({
        "resumes_directory": str(get_resumes_dir()),
        "templates_directory": str(get_templates_dir()),
        "pdflatex_installed": pdflatex is not None,
        "pdflatex_path": pdflatex,
        "env_vars": {
            "LATEX_RESUME_DIR": "Set to customize resumes directory",
            "LATEX_TEMPLATES_DIR": "Set to customize templates directory"
        }
    }, indent=2)

Tool Definition Quality

B3.3/5.0
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 this is a 'Get' operation, implying read-only behavior, but doesn't specify whether it requires permissions, has side effects, returns structured data, or handles errors. For a configuration tool with zero annotation coverage, this leaves significant behavioral gaps.

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 wasted words. It's front-loaded with the core purpose and includes specific details about what's retrieved. Every element earns its place without redundancy or unnecessary elaboration.

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?

Given the tool has 0 parameters, 100% schema coverage, and an output schema exists, the description is reasonably complete. It specifies what configuration data is retrieved, which addresses the core purpose. However, without annotations and with behavioral gaps, it could benefit from more context about usage patterns or return format, though the output schema mitigates some of this.

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 with 100% schema description coverage, so the schema fully documents the absence of inputs. The description adds value by specifying what configuration information is retrieved ('directories and pdflatex status'), which goes beyond the empty schema. This compensates appropriately for the parameter-less design.

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 with a specific verb ('Get') and resource ('current configuration'), including what information is retrieved ('directories and pdflatex status'). It distinguishes from siblings like 'get_template' or 'read_resume' by focusing on system configuration rather than resume data. However, it doesn't explicitly differentiate from all siblings in the description text itself.

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, appropriate contexts, or exclusions. Given the sibling tools are all resume-related operations, the implicit context might be checking system configuration before resume operations, but this is not stated.

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