Skip to main content
Glama
Sign In
Tessie MCP Server

Tessie MCP Server

by akrowczyk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

set_bioweapon_mode

Enable or disable Bioweapon Defense Mode on your Tesla, automatically waking the car if it's asleep.

Instructions

Enables or disables Bioweapon Defense Mode — 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_bioweapon_mode"
  }
}

Input Schema

NameRequiredDescriptionDefault
onYesEnable or disable
vinNoVehicle Identification Number (VIN). Defaults to TESSIE_DEFAULT_VIN env var if set.
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.8/5.0
Behavior3/5

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

With no annotations, the description carries full burden for behavioral disclosure. It notes 'auto-wakes if asleep' and implies mutation, but does not mention permissions, reversibility, or other side effects. This is moderate transparency.

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 a single front-loaded sentence with no redundant words. It conveys the core action and a valuable behavioral note efficiently.

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

Completeness4/5

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

The tool is a simple toggle with all parameters documented in the schema. The description provides the essential action and the auto-wake behavior, sufficient for an agent to select and invoke the tool. However, no output schema or return value details are given, and prerequisites or other side effects are not explained, preventing a perfect score.

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 input schema documents all 4 parameters with 100% coverage, so the baseline is 3. The description adds no parameter-specific information beyond what the schema already provides.

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 identifies the action ('Enables or disables') and the resource ('Bioweapon Defense Mode'), distinguishing it from all sibling tools. The additional note about auto-waking further defines the tool's behavior.

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?

No explicit guidance on when to use this tool versus alternatives, but the name and description make the use case obvious. The auto-wake note implies it works on sleeping vehicles, but no exclusions or alternatives are mentioned.

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