Skip to main content
Glama
Sign In

AskMyEV

by com.askmyev
OverviewDiscussionsAdmin

List my cars

list_vehicles
Read-only

List the Tesla vehicles connected to AskMyEV. Standard covers up to 3 cars on the owner's Tesla account and Fleet up to 10 (owners who connected before Oct 21, 2026 keep all their cars), with daily limits shared across them.

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": "list_vehicles"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare this a safe read-only operation, and the description adds plan-tier caps (3 standard, 10 fleet) and a note about shared daily limits. However, it does not explain what those daily limits affect, what happens when they are hit, or what the returned vehicle objects contain.

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?

The purpose is front-loaded in the first sentence, and the plan-limit details are placed afterward as supporting context. The parenthetical is slightly dense but relevant to how many vehicles may be returned.

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?

For a zero-parameter read-only tool this is mostly complete, but with no output schema the description should say what each vehicle record includes, such as ID, name, model, or connection status. The plan-limit note is useful but does not compensate for that missing return-value context.

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?

There are zero parameters, so the baseline is 4. The description has no parameter semantics to add, and none are needed.

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 uses a specific verb and resource: "List the Tesla vehicles connected to AskMyEV." That is clear, but the second sentence shifts into plan caps and limits rather than differentiating this from siblings such as get_vehicle_status or get_vehicle_location.

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?

Enumeration is implied by "List the Tesla vehicles," but the description gives no explicit when-to-use guidance or alternatives. It does not say whether to call this before get_vehicle_status or how it differs from related vehicle-reading tools.

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