mcp-tirepressure
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 |
|---|---|
| get_bikesA | List all configured bike profiles (name, tire/rim specs, style). |
| get_bikeA | Get a single bike profile by name. Returns specs + bike weight. |
| calc_pressureB | Calculate recommended tire pressure (front/rear in bar) for a given bike, rider weight, and surface (DRY/WET/SNOW). Applies hookless rim cap where needed. |
| get_recommended_pressureB | One-call recommended pressure with live weather. Fetches Open-Meteo data, determines wet/dry, and returns front/rear pressure in bar. |
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_bikes and get_bike are clearly distinct list-vs-detail tools, but calc_pressure and get_recommended_pressure overlap noticeably. Both return front/rear pressure recommendations; the key difference is explicit surface vs live weather, which is described but could still cause selection ambiguity.
Tool names mostly follow a get_/calc_ verb_noun pattern, and the get_bikes/get_bike pair is nicely consistent. calc_pressure uses an abbreviation rather than calculate_pressure and get_recommended_pressure includes an adjective, so there are minor deviations but no chaotic mixing.
Four tools is well-scoped for a niche tire-pressure server with no bloat or obvious excess. Each tool has a distinct role in listing bikes, retrieving bike details, manual calculation, and weather-driven recommendation.
The core workflow of retrieving bike profiles and getting pressure recommendations is covered, including both manual surface input and live weather. The main gap is the lack of bike profile creation/update/delete, though profiles may be externally configured.