AskMyEV

Car status

get_vehicle_status

Read-only

Battery, range, charging, tire pressures, temps and software for the car. Uses live data if the car is awake (or streamed data from the last 2 minutes), otherwise the latest saved snapshot. Fair use: up to 20 live checks per day for the whole account (all cars together), then saved data. Never wakes the car unless wake=true (only when the user explicitly asks for fresh data from a sleeping car; 1 wake per day for the whole account, 3 on Fleet, shared with car controls).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_vehicle_status"
  }
}

Input Schema

Name	Required	Description	Default
`vin`	No	Vehicle VIN (full, or its last 4-6 characters). Required when the account has more than one car (call list_vehicles first and ask the user which car). Optional with one car. Every car on the owner's Tesla account is covered by the plan.
`wake`	No	Wake a sleeping car. Only if the user explicitly asked.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 3, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds substantial context beyond that: the 20-live-checks-per-day account-wide quota, the 1-wake-per-day (3 on Fleet) budget shared with car controls, and the guarantee that the car is never woken unless wake=true. These are exactly the side effects and rate limits an agent needs before calling.

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

Conciseness4/5

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

It is front-loaded with what data is returned, then freshness rules, then quota limits — a sensible order with no filler sentences. The middle sentence is a dense run-on with stacked parentheticals, which slightly slows parsing, but every clause carries information.

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?

With no output schema, the description carries the return-value burden and does enumerate the data categories returned (battery, range, charging, tire pressures, temps, software) along with how fresh they are. Combined with the rate-limit and wake policy, an agent has everything needed to decide whether and how to call it.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description adds real meaning beyond the schema for wake: the explicit 'never wakes the car unless wake=true' default and the shared daily wake budget that makes waking a costly action. It adds little for vin beyond what the schema already says about multi-car disambiguation.

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

Purpose4/5

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

The description opens with a specific verb-less but concrete resource enumeration: battery, range, charging, tire pressures, temps and software — an agent can tell this is a single-car status snapshot rather than a history/trend tool. It never names a sibling (battery_trend, tire_pressure_trend, get_controls_status) explicitly, so the differentiation is implied by the field list rather than stated.

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

Usage Guidelines5/5

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

It gives explicit when-to-use rules: live data when the car is awake or data is streamed within 2 minutes, otherwise the saved snapshot, and it states the precise condition for wake=true ('only when the user explicitly asks for fresh data from a sleeping car'). It also documents the hard fallback behavior (20 live checks/day then saved data), which tells the agent what happens when the preferred path is exhausted.

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

All AskMyEV tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?