Lathe
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| lathe_templatesA | List the resume templates currently available in the Lathe templates folder. |
| lathe_previewA | Open a live browser window showing a rendered resume. Pass the structured resume data and the template name (from lathe_templates). The window stays open so subsequent lathe_shape calls refresh it in place. |
| lathe_shapeA | Push updated resume data (and optionally a different template) into the live preview. The browser window auto-refreshes so the user sees the change immediately. Use this after every feedback iteration. |
| lathe_finishA | Export the current preview as a PDF. Defaults to the output/ folder; pass folderPath to organize into subfolders. |
| lathe_add_templateA | Save a new HTML template into the templates folder. The HTML can use Handlebars placeholders like {{basics.name}} or {{#each work}}…{{/each}}. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a distinct purpose: listing templates, creating a live preview, updating the preview, exporting to PDF, and adding new templates. There is no overlap or ambiguity between them.
All tools share the 'lathe_' prefix and use snake_case, but the first tool 'lathe_templates' uses a noun instead of a verb, while others use verbs like 'preview', 'shape', 'finish', and 'add_template'. This minor inconsistency is easy to overlook.
Five tools cover the complete workflow of template management, previewing, iterative updates, and PDF export. The count is well-scoped and each tool contributes a necessary function.
The tool set covers the full lifecycle: discover templates, preview, edit data, export, and add custom templates. There are no obvious missing operations for the intended resume rendering use case.