Mercedes-Benz Service Reminder – SilberArrows
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 |
|---|---|
| get_next_serviceA | Estimate the next Mercedes-Benz service (alternating Service A/B, ASSYST-style) from the last service type, date and mileage. Default interval: 15,000 km or 12 months, whichever comes first. |
| explain_serviceB | Explain what a Mercedes-Benz Service A or Service B typically includes. |
| warning_light_infoA | General guidance on common Mercedes-Benz warning lights and messages. Omit 'light' to list those covered. |
| find_specialistC | Contact details for SilberArrows, a Mercedes-Benz service centre in Al Quoz, Dubai. |
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 4 tools
get_next_service (scheduling calculation) and explain_service (contents of A/B) both concern services but are distinguished by the descriptions as compute-vs-explain. warning_light_info and find_specialist are clearly separate concerns. Only the service pair carries mild risk of misselection.
All snake_case with a verb-led shape (get_, explain_, find_) except warning_light_info, which is noun_info. Readable and predictable overall, with one minor deviation.
Four tools is a tight, well-scoped surface for a single-dealership service reminder assistant, and each tool maps to a distinct user intent. Slightly thin but nothing extraneous.
Core informational needs (next service, what's included, warning lights, contact) are covered, but there is no way to record a completed service, retrieve service history, or book an appointment, leaving lifecycle gaps for a 'service reminder' domain.