TeslaMate MCP Server

Overview Schema Source Related Servers Discussions Admin

Tesla Tpms Status

tesla_tpms_status

Retrieves current tire pressure readings from TeslaMate, warning if any tire is below minimum, above maximum, or deviates from average by 0.15 bar.

Instructions

Current TPMS pressures with warnings for anomalies.

Reads from the latest position record in TeslaMate. Warns if any tyre is below TESLA_TPMS_MIN_THRESHOLD or above TESLA_TPMS_MAX_THRESHOLD, or differs from the average by > 0.15 bar.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`car_id`	No	Filter by vehicle ID (default: TESLA_CAR_ID env or first car)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 13, 2026

TDQS

A4.1/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full behavioral burden. It transparently discloses the data source ('latest position record in TeslaMate') and the warning logic, including threshold sources and the >0.15 bar deviation rule. It does not cover auth requirements or failure modes, but this is a read-only status tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with purpose, then adds source and warning criteria in compact sentences. Every sentence earns its place by explaining behavior the agent needs to interpret the output correctly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the low complexity, 100% schema coverage, and an output schema, the description supplies enough context: what is returned, where it comes from, and how anomalies are identified. No critical agent-facing detail is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 100% description coverage for the single car_id parameter, so the baseline is 3. The description does not add any parameter meaning beyond the schema, such as default resolution behavior or filtering semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific resource ('TPMS pressures') and temporal scope ('Current'), which distinguishes it from the sibling tesla_tpms_history. An agent can tell this tool reports present tyre pressure status rather than historical data.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage through 'Current TPMS pressures,' but it does not explicitly say when to choose this over tesla_tpms_history or other status tools. No when-not or alternative guidance is provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server