Skip to main content
Glama

EV charging cost calculator

ev_charging_cost_calculator
Read-onlyIdempotent

Cost to drive an electric car a given distance. All inputs are required so nothing is assumed.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "miles": "<miles>",
      "miles_per_kwh": "<miles_per_kwh>",
      "price_pence_per_kwh": "<price_pence_per_kwh>"
    },
    "name": "ev_charging_cost_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
milesYesdistance in miles
miles_per_kwhYescar efficiency
price_pence_per_kwhYeselectricity price in pence per kWh

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 readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without the description. The description adds only the note that no defaults are assumed, and says nothing about the currency/units of the result or rounding, which matters for a cost calculator.

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?

Two short sentences, front-loaded with the purpose, with no filler. The second sentence is close to restating the required array but still earns its place as a warning against expecting defaults.

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 simple closed-world arithmetic tool with full schema coverage and no output schema, the description is mostly sufficient. The notable gap is the output: it never states that the result is a cost in pence (consistent with the input price unit), leaving the return unit to inference.

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% with per-parameter descriptions (miles, efficiency, price in pence per kWh), so the baseline is 3. The sentence 'All inputs are required so nothing is assumed' reinforces the required/fully-specified contract beyond the schema's required array, adding mild value.

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 concrete computation (cost to drive) bound to a specific resource (electric car, i.e. EV charging), which implicitly separates it from the sibling fuel_cost_calculator. It is clear what the tool produces, though it never names an alternative explicitly.

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?

Usage is only implied by the framing 'cost to drive an electric car a given distance' – an agent can infer this is the EV counterpart to a fuel cost calculation. There is no explicit when-to-use, when-not, or pointer to the fuel_cost_calculator sibling.

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