Spec3 MCP Server
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_car_contextA | Get information about the user's 1994 BMW E36 325is Spec3 race car build. Returns current configuration, build status, modifications, and car-specific details. Call this tool when providing personalized advice, troubleshooting, or planning modifications. Returns: dict: Car configuration, history, and current state |
| list_documentsA | List all available Spec3 racing reference documents. Available documents include: Spec3 Constructor's Guide, Bentley E36 Manual, 2025 NASA CCR rules, and 2025 Spec3 class rules. Returns: dict: Document IDs, names, and descriptions |
| get_documentA | Retrieve full text and visual content of Spec3 racing reference documents. Fetches complete PDF content from S3 including text and page images. Page images preserve diagrams, tables, and formatting that text extraction cannot capture. Args: document_id: Document ID from list_documents (e.g., "spec3_rules") page_start: Starting page number (default: 1) page_end: Ending page number (default: None for all remaining pages) include_images: Include page images for diagrams/tables (default: True) Returns: dict: Document text, page images (base64), metadata, and page range |
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 3 tools
Each tool has a clearly distinct purpose with no overlap: get_car_context retrieves car-specific build information, list_documents lists available reference documents, and get_document fetches detailed content from those documents. The descriptions explicitly differentiate their scopes, making tool selection unambiguous.
All tools follow a consistent verb_noun pattern (get_car_context, get_document, list_documents) using snake_case throughout. The naming is predictable and readable, with verbs appropriately matched to actions (get for retrieval, list for enumeration).
Three tools is a minimal but reasonable count for a specialized server focused on Spec3 racing information. It covers core needs (car context, document listing, and document retrieval), though it might feel slightly thin if expanded functionality (e.g., update or search tools) were expected for broader use cases.
The tool set provides complete coverage for retrieving Spec3 racing information: get_car_context handles car-specific data, while list_documents and get_document manage reference documents. A minor gap exists in lacking update or modification tools for the car context, but the retrieval-focused scope is well-defined and functional for its purpose.