Skip to main content
Glama
Sign In
Tessie MCP Server

Tessie MCP Server

by akrowczyk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

set_cabin_overheat_protection

Enable or disable Cabin Overheat Protection in a Tesla, optionally using fan-only mode. Wakes the vehicle if asleep to apply the setting.

Instructions

Enables or disables Cabin Overheat Protection — auto-wakes if asleep

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "on": "<on>"
    },
    "name": "set_cabin_overheat_protection"
  }
}

Input Schema

NameRequiredDescriptionDefault
onYesEnable or disable
vinNoVehicle Identification Number (VIN). Defaults to TESSIE_DEFAULT_VIN env var if set.
fan_onlyNoFan only mode (no A/C)
max_attemptsNoMaximum retry attempts
wait_for_completionNoWait for the command to complete before returning

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.5/5.0
Behavior3/5

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

The description discloses one useful behavior ('auto-wakes if asleep'), which is not captured by the schema or annotations. However, it does not elaborate on other potential side effects, permissions, or failure modes, leaving significant gaps for a command tool with no annotations to rely on.

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 exactly one sentence, front-loading the main purpose and adding a single behavioral note. No redundancies or wasted words; it is appropriately sized for the tool's simplicity.

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

Completeness3/5

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

While the core purpose is clear and parameters are well-documented in the schema, the overall tool context is thin: no output schema, no annotation support, and the description does not explain the command's full behavior or prerequisites beyond the auto-wake note. For a simple toggle this is adequate but not complete.

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 descriptions cover all five parameters clearly (e.g., 'on' described as 'Enable or disable', 'fan_only' as 'Fan only mode (no A/C)'), so the description adds no additional parameter guidance. Baseline of 3 is appropriate since the schema fully documents the parameter meanings.

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 clearly states the action ('Enables or disables') and the specific resource ('Cabin Overheat Protection'), and it is distinct from sibling commands like start_climate or set_temperatures. The verb and resource are specific and unambiguous.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives, nor are there any prerequisites or exclusion conditions mentioned. The description only restates the function without helping the agent select it appropriately among the many sibling set_* commands.

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

Deploy Server

Other Tools