MaCalculatriceEnLigne

calculate_ev_charging_cost

Compute electric vehicle charging cost and time to full. Use for EV trip planning. Inputs: battery kWh, current %, target %, charger kW, kWh price. Returns cost and hours. See list_bundles for related 'energie' calculators.

Input Schema

TableJSON Schema

Name	Required	Description
`price_kwh`	No	Price per kWh
`target_pct`	No	Target charge %
`battery_kwh`	Yes	Battery capacity kWh
`current_pct`	Yes	Current charge %

Output Schema

TableJSON Schema

Name	Required	Description
`result`	No	Computed result. Object whose fields depend on the tool (e.g. {tax, marginal_rate, brackets} for tax tools, {volume_l, gallons} for volume tools).
`source`	No	Authoritative source for the rule or formula (e.g. "Article 197 CGI", "NF DTU 21").
`formula`	No	Human-readable formula or method used (e.g. "I=P·r·t", "Magnus formula").
`reference_url`	No	Link to a calcul2 page documenting the calculation in detail.

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 13, 2026

TDQS

A4.1/5.0

Behavior4/5

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

No annotations provided, but the description indicates it returns cost and hours with no side effects. It lacks details on input validation or edge cases, but the tool is a simple calculator, so behavioral traits are largely inferred.

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 description is short and lists inputs and outputs efficiently. One extraneous input mention wastes a bit of conciseness, but overall it's well-structured.

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?

Despite having an output schema, the description explains return values. However, the incorrect 'charger kW' input and lack of clarification about default values (though in schema) leave room for confusion, making it only moderately complete.

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

Parameters2/5

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

The description mentions 'charger kW' as an input, which is not present in the input schema. This introduces confusion and misleads about required parameters. Schema descriptions already cover the four actual parameters.

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 states the tool computes EV charging cost and time, with a specific verb and resource. It distinguishes itself from sibling calculators by focusing on EV trip planning.

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?

The description explicitly says 'Use for EV trip planning' and directs to 'list_bundles' for related calculators, providing when-to-use and alternative references.

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

All MaCalculatriceEnLigne 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.