Skip to main content
Glama
Sign In

AskMyEV

by com.askmyev
OverviewDiscussionsAdmin

Where's my car

get_vehicle_location
Read-only

The car's current location (live, only if the car is awake). Works only if the owner turned location on, during setup or on their AskMyEV Account page; otherwise it explains how. AskMyEV doesn't save the coordinates and never wakes the car for this.

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_location"
  }
}

Input Schema

NameRequiredDescriptionDefault
vinNoVehicle 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Goes well past the readOnlyHint annotation by disclosing that AskMyEV does not persist coordinates and never wakes the vehicle for this request, plus the opt-in prerequisite and the explanatory fallback behavior. These are exactly the behavioral traits an agent needs to set user expectations and avoid promising stale or unavailable data.

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?

Three tight sentences, front-loaded with what is returned and its liveness condition, followed by the prerequisite and the privacy behavior. Every clause carries information; nothing is repeated from the schema or annotations.

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?

For a one-optional-param read tool with annotations and no output schema, the description covers freshness, prerequisites, privacy, and fallback behavior. The remaining gap is the shape of the returned value (raw coordinates vs. an address or map reference), which an agent would want since no output schema exists.

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?

Schema coverage is 100% and the vin property already documents the full-or-last-4-6-characters format and the list_vehicles-first flow for multi-car accounts. The description adds no parameter meaning beyond that, so the baseline 3 applies.

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?

States a specific verb and resource ('current location') with the key qualifier 'live, only if the car is awake', which separates it from get_vehicle_status and the history/trend siblings. It stops short of naming any sibling explicitly, so the differentiation is inferable 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 Guidelines4/5

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

Makes the preconditions explicit: the car must be awake, and the owner must have enabled location sharing during setup or on the account page, with a fallback that 'it explains how'. It gives clear context for when the call will succeed but does not point to an alternative tool when the precondition fails.

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

All AskMyEV toolsInspect
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