Skip to main content
Glama
jiweiqi

heatpump-mcp-server

by jiweiqi
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

estimate_energy_costs

Compare annual electricity costs and payback period of a heat pump versus your current heating system, with monthly breakdown and 10-year savings projection.

Instructions

Estimate annual electricity costs and payback period for heat pump vs current heating system.

Analyzes:

  • Monthly heating load based on location and home characteristics

  • Heat pump electricity consumption using model's efficiency (HSPF2)

  • Comparison with current heating fuel costs

  • 10-year cost projection with savings analysis

  • Break-even year calculation

Returns: Dictionary with: - location_info: Climate and location details - electricity_rate: Rate used for calculations ($/kWh) - gas_rate: Comparison fuel rate if applicable - heat_pump_info: Selected model specifications - monthly_breakdown: Month-by-month cost comparison - annual_summary: Annual totals and payback analysis - ten_year_projection: Long-term savings projection - calculation_notes: Important assumptions and notes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
zip_codeYes5-digit US ZIP code
square_feetYesHome square footage (100-10000)
build_yearYesYear home was built (1900-2025)
heat_pump_modelYesSelected heat pump model name
gas_price_per_thermNoLocal gas price per therm ($)
electricity_rate_overrideNoManual electricity rate ($/kWh)
current_heating_fuelNoCurrent heating fuel: gas, oil, propane, electricgas

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Tool Definition Quality

A4/5.0
Behavior3/5

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

No annotations provided, so description carries the burden. It details output structure but omits behavioral traits like data sources, limits, or assumptions beyond mentioning 'calculation_notes'.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is well-structured with bullet points, front-loaded purpose, and every sentence adds value without fluff.

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?

Given 7 parameters, 4 required, and a full output schema described, the description is thorough. Minor omission: no mention of rate defaulting or fallback behavior.

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 covers 100% of parameters, and description adds context by grouping parameters into analysis steps, enhancing meaning beyond the schema alone.

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 estimates annual electricity costs and payback period for heat pump vs current system, and lists detailed analysis areas. It distinguishes from sibling tools like sizing calculators.

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?

The description implicitly conveys usage for cost comparison, but lacks explicit guidance on when not to use or alternatives among sibling tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jiweiqi/heatpump-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server