Skip to main content
Glama

Fox River Press

Estimate home EV charging

home_charging_estimate
Read-onlyIdempotent

What a home circuit delivers to an electric car and what it costs: charger amps on a breaker by the 80 percent rule, kilowatts, miles of range per hour, cost per mile, monthly cost and the gas price at which a gas car costs the same per mile. Every assumption has a stated default and can be replaced.

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

Input Schema

NameRequiredDescriptionDefault
voltsNo120 for a regular outlet, 240 for Level 2. Default 240.
gas_car_mpgNoThe gas car to compare against. Default 28.
breaker_ampsNoThe circuit's breaker, one of 15, 20, 30, 40, 50, 60, 70, 80, 100. The charger draws 80 percent of it. Default 40.
cents_per_kwhNoElectricity price. Default 18.2 (U.S. residential average, 2026 (EIA projection)).
miles_per_dayNoDefault 35.
kwh_per_100_milesNoThe car's efficiency. Default 30 (example; your car's figure is on its fueleconomy.gov label).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds genuine behavioral context beyond that: this is a pure calculation whose every input defaults, so it is callable with zero arguments, and the return set is explicitly enumerated, which matters because no output schema exists. It stops short of stating units for the cost figures.

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?

One dense but well-ordered sentence: it leads with what the circuit delivers, then what it costs, then the break-even comparison. The closing sentence about defaults is high-value and short. Nothing is wasted, though the single-sentence block is harder to scan than a short lead plus bullets would be.

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?

With zero required parameters, full schema coverage and no output schema, the description is nearly self-sufficient: it enumerates the results so the agent knows what comes back and confirms the all-defaults calling pattern. Only the units of the cost and break-even outputs are left unstated, a minor gap for a read-only calculator.

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 each of the six parameters already carries a description and default value, so the schema does the heavy lifting. The description reinforces the 80 percent breaker rule and the replaceable-defaults model, but adds no syntax, ranges or units beyond what the schema states. 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?

The description names the domain (home EV charging) and enumerates the concrete outputs: charger amps under the 80 percent rule, kilowatts, miles of range per hour, cost per mile, monthly cost and the gas-price break-even. That is specific enough to distinguish it from a pure cost tool. It does not, however, contrast itself with the adjacent compare_chargers sibling, so an agent must infer the boundary.

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: 'Every assumption has a stated default and can be replaced' tells the agent it can call with no arguments and override selectively, which is real guidance. There is no explicit statement of when to pick this over compare_chargers or another comparison tool, and no exclusions.

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