Workshop Assistant
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_jobsA | Search job cards in the workshop. Args: status: One of booked, in_progress, waiting_parts, completed, invoiced. Use "open" for anything not yet finished. reg: Registration plate, full or partial (e.g. "LM19" or "LM19 KTZ"). technician: Technician name, full or partial. limit: Maximum number of job cards to return. |
| vehicle_historyA | Full service history for one vehicle, newest first. Use this to answer questions like "has this car been in before for the same fault?" - repeat visits for one symptom are the useful signal. Args: reg: Registration plate, full or partial. |
| parts_availabilityA | Look up parts stock. Args: query: Part name or SKU, full or partial. Omit to list everything. only_low_stock: If true, return only parts at or below reorder level. |
| jobs_blocked_on_partsA | Open job cards that cannot proceed because a required part is short. This is the question a service manager actually asks each morning, and it is the reason the assistant is worth having: answering it by hand means cross-referencing every open job against the stock list. |
| technician_scheduleA | Workshop bookings for a given day. Args: day: ISO date (YYYY-MM-DD), or "today" / "tomorrow". Defaults to today. technician: Technician name, full or partial. Omit for the whole workshop. |
| add_job_noteA | Add a note to a job card. The only tool here that changes anything. It is narrow on purpose: it can append a note and nothing else. It cannot alter a job's status, its parts or its price - those are decisions that need a person. Args: job_card: The job card ID to attach the note to. note: The text of the note. author: Who the note is from. |
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 6 tools
Each tool targets a distinct query: jobs, vehicle history, parts stock, blocked jobs, schedule, and notes. The overlap between search_jobs and jobs_blocked_on_parts is minimal because the latter is a specific cross-reference of open jobs against parts shortages, making their purposes clearly separable.
All tool names use snake_case and are descriptive, but they mix verb-noun (search_jobs, add_job_note) with noun-noun (vehicle_history, parts_availability) forms. The style is consistent and no naming is chaotic, though a stricter verb_noun pattern would make it fully predictable.
With 6 tools, the server is well-scoped for a workshop assistant. Each tool serves a clear purpose and there is no bloat or sense of missing essential tools for the intended read-heavy, note-taking workflow.
The surface covers the core informational needs: job search, vehicle history, parts availability, blocked jobs, and technician schedules, plus a narrow note-adding action. It intentionally excludes job creation or status changes, which is clearly stated, so only minor gaps exist for full lifecycle management.