Skip to main content
Glama

Electric car models listed on the public EV Database home

auto_ev_database
Read-only

Electric car models listed on the public EV Database home page: make, model name (with battery size where listed), availability text and EV-Database detail URL. Only the models on that page are returned; specs such as range are not on the list. Related tools on this server, for a different need: auto_carfax when you need CARFAX used-car listings by body style or price ceiling; auto_carsdirect_vehicle when you need CarsDirect used-car listings near a US ZIP code: vehicle. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax models, 1 to 100 (default 20)

Output Schema

NameRequiredDescriptionDefault
countNo
modelsNo
sourceNo
checkedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond readOnlyHint/openWorldHint by disclosing the coverage limit (only what is on that page, no specs such as range) and the billing behavior ($0.002 per successful call via x402, failed calls not charged, with the payment networks listed). The cost and partial-coverage traits are exactly the kind of context an agent cannot infer from annotations or schema.

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?

Front-loads what is returned before the caveats and alternatives, and every sentence carries information (scope, exclusion of specs, alternatives, pricing). The final pricing sentence is long and network-heavy, slightly diluting the otherwise tight structure.

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?

For a read-only, one-optional-parameter listing tool with an output schema and readOnlyHint/openWorldHint annotations, the description supplies the remaining essentials: coverage boundaries, what is absent from the response, cost, and alternative tools. Nothing an agent needs in order to decide and call correctly is missing.

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 has full description coverage for the single 'limit' parameter (max models, 1 to 100, default 20), so the description need not restate it. The description adds no meaning about how limit interacts with the page's model list, so this is the baseline 3 for a well-documented single parameter.

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?

States a specific resource and scope: electric car models listed on the public EV Database home page, and enumerates the returned fields (make, model name with battery size, availability text, detail URL). It also names the sibling tools (auto_carfax, auto_carsdirect_vehicle) so an agent can distinguish this listing tool from the used-car listing tools.

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?

Explicitly routes the agent elsewhere for different needs, quoting the selection condition for auto_carfax (CARFAX listings by body style or price ceiling) and auto_carsdirect_vehicle (listings near a US ZIP). It also bounds the use case with 'Only the models on that page are returned; specs such as range are not on the list.' No guidance is given about the other EV-related siblings (e.g. auto_data_wa_gov_electric_vehicle, auto_plugshare), but the alternatives it does name are clearly conditioned.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources