startline
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 |
|---|---|
| list_eventsA | List all events in the vault with document counts. |
| event_overviewA | Summarise one event: categories with doc counts, plus any amendments. Args: event: Event code, e.g. 'AUS-GP-2026' (see list_events). |
| list_docsA | List documents, optionally filtered by event and/or category substring. Args: event: Event code filter, e.g. 'AUS-GP-2026'. category: Substring match on the category path, e.g. 'briefing' or 'supplementary-regulations'. include_superseded: Include documents replaced by newer versions. |
| searchA | Full-text search over every document chunk (FTS5 + BM25 + synonyms). Best first step for any factual question. Results cite note + page heading; follow up with read_doc for full context. Args: query: Plain words, e.g. 'sign on saturday' or 'pit lane speed limit'. event: Optional event code filter. category: Optional substring filter on category path. include_superseded: Also search documents replaced by newer versions. limit: Max results (default 8). |
| read_docA | Read a document's full text by slug or title (fuzzy matched). Args: name: Slug or title, e.g. 'marshals event information booklet' or '2026-mxm-event-sat-v1-a6-device'. event: Optional event code to disambiguate. pages: Optional page range like '3-5' or '12' to return only those '## Page N' sections (recommended for long documents). |
| schedule_forA | Timeline for one event day, parsed from the current Minute-x-Minute. Args: day: 'friday' / 'fri' / 'saturday' / 'sat' / 'sunday' / 'thursday'. event: Event code, e.g. 'AUS-GP-2026'. query: Optional filter — only entries containing this substring, e.g. 'marshal' or 'supercars'. |
| amendmentsB | All amendment documents for an event and what they amend. Args: event: Event code, e.g. 'AUS-GP-2026'. |
| diff_amendmentA | What an amendment actually changed vs the schedule it amends: moved/added/removed timeline rows plus a short summary. Cached. Args: name: Slug or title of the amendment document (see amendments()). event: Optional event code to disambiguate. |
| doc_historyB | Version chain for a document: current version, superseded ones, and amendments pointing at it. Args: name: Slug or title of any version of the document. event: Optional event code to disambiguate. |
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 9 tools
Each tool targets a distinct resource and action: events, documents, search, schedules, amendments, and history. Overlap is minimal and clarified by descriptions (e.g., event_overview vs. list_docs).
Names mix conventions: list_events, list_docs, read_doc, diff_amendment follow verb_noun, while event_overview, schedule_for, amendments, and doc_history do not. However, all names are still descriptive and readable, so the inconsistency is moderate rather than chaotic.
Nine tools is well within the ideal 3–15 range. Each tool serves a clear purpose in the event-documentation domain, and none feel redundant or unnecessary.
The domain is a read-only knowledge base for motorsport events, and the set covers event listing, document search/read, per-day schedules, amendments, and version history. No obvious workflow dead ends remain; even superseded documents and amendment diffs are handled.