mcPER
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCPER_DATA_DIR | No | Location of the generated data directory (`data/pack`) when it is placed outside the mcPER directory, e.g. "/path/to/pack". If omitted, the bundled/default `data/pack` location is used. |
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 |
|---|---|
| decode_vinB | Decode a VIN using ePER chassis data: model, MVS version, catalogue(s), build date, engine number, organization number, colours and factory options (CARATT). |
| list_cataloguesA | List catalogues (model ranges). Filter by sub-make (F=Fiat, T=Fiat Commercial, L=Lancia, R=Alfa Romeo, C=Abarth) and/or text in the description. |
| list_groupsB | List the main groups of a catalogue (engine, brakes, body, ...). |
| list_subgroupsC | List the subgroups of a group in a catalogue. |
| list_tablesB | List the parts tables (drawings) of a subgroup, with their applicability. Pass vin to see which tables fit the vehicle. |
| get_table_partsB | Get the parts list of a table (drawing): reference number, part number, quantity, description, notes, option pattern and modifications. Pass vin to evaluate fitment for that vehicle. |
| search_partsA | Search a catalogue for parts by description words (all words must match; Japanese or English) or by part number prefix. ePER Japanese names are terse katakana (e.g. "パッド セット" for brake pads, "フィルタ" for filters); if nothing matches, retry with a shorter word or English ("PADS", "OIL FILTER"), or browse groups. With vin the catalogue is taken from the VIN and results are sorted by fitment. |
| get_partB | Get details of a part number: description, family, unit, weight, counts of supersessions, and the components if it is an assembly. |
| get_part_historyB | Follow the supersession (replacement) chain of a part number in both directions: which numbers replaced it (with dates, quantity ratios and interchangeability) and which older numbers it replaced. current_parts lists the end(s) of the chain. |
| where_usedC | List the catalogue tables where a part number is used, and assemblies/kits that contain it. |
| get_modificationA | Describe a modification code (from a MODIF field such as "D2105") and its cut-over points (build date, chassis, engine, organization number). |
| get_drawing_imageA | Show the exploded-view drawing of a parts table (same keys as get_table_parts). The reference numbers of the given parts are framed in red so the user can see where they are. |
| get_assembly_imageB | Show the exploded view (cliché) of an assembly part, e.g. a brake caliper with its pads and seals (parts with has_components or inside_assembly). Component reference numbers can be framed in red. |
| list_languagesA | List languages available in the catalogue. |
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 14 tools
The tools mostly target clearly distinct operations: hierarchical browsing (groups, subgroups, tables), content retrieval (table parts, part details), search, VIN decoding, supersession history, where-used, and images. The only mild overlaps are get_part/get_part_history/where_used (related but different facets) and get_drawing_image/get_assembly_image (both render exploded views but for different entity types), which descriptions clarify well.
Almost all tools follow a predictable snake_case verb_noun pattern (list_groups, get_table_parts, search_parts, decode_vin), with a few acceptable noun-centric variants like get_part_history and get_drawing_image. The outlier is where_used, which is a query phrase rather than a verb_noun name, but it remains readable and clear.
At 14 tools, the set is well-scoped for a read-only parts catalogue: it covers browsing, search, VIN decoding, part relationships, and imagery without bloat. Each tool has a distinct role and no redundant near-duplicates pad the surface.
The surface covers the full read-only lifecycle: catalogue navigation, VIN-based fitment, part lookup, supersession history, where-used, modification codes, and exploded views. Minor gaps remain—there is no direct lookup by vehicle attributes (e.g., model/year) without a VIN, and no explicit operation to resolve a table reference number to a part outside get_table_parts—but these are workarounds rather than dead ends.