Skip to main content
Glama
jiweiqi

heatpump-mcp-server

by jiweiqi
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

calculate_multi_zone_sizing

Calculate heating and cooling loads for each zone in a multi-zone home. Get zone-by-zone analysis, system recommendations, and climate-specific data to design an efficient heat pump system.

Instructions

Calculate heating/cooling loads for a multi-zone home with detailed zone-by-zone analysis.

Each zone should specify:

  • name: User-defined zone name

  • square_feet: Zone area (50-5000 sqft)

  • ceiling_height: Height in feet (7-20 ft, default 8)

  • zone_type: living_area, bedrooms, kitchen, basement, attic, garage, other

  • sun_exposure: north, south, east, west, minimal

  • window_coverage: Percentage of wall area as windows (0.0-0.5, default 0.15)

  • occupancy: high, medium, low

  • heat_sources: List like ["kitchen_appliances", "electronics", "home_office"]

  • air_sealing: tight, average, leaky

  • is_above_grade: True if above ground level

Returns: Dictionary with: - total_cooling_load/total_heating_load: Total BTU requirements - zone_results: Detailed results for each zone - system_options: Recommended multi-zone configurations - climate_info: Location-specific climate data - recommendations: Installation and design recommendations

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
zip_codeYes5-digit US ZIP code
build_yearYesYear home was built (1900-2025)
zonesYesList of zone configurations

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Tool Definition Quality

A4.1/5.0
Behavior4/5

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

No annotations provided; description fully explains inputs and outputs including zone structure and return values, but does not mention computational constraints or error conditions.

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?

Well-structured with clear breakdown of zone specification and return results, though somewhat lengthy; no wasted sentences.

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?

Output schema exists (not shown) but description provides full return structure. For a complex multi-zone tool, covers essential inputs and outputs adequately.

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 all 3 parameters with descriptions, but zones parameter schema is minimal (additionalProperties: true). Description adds extensive detail on zone sub-fields, compensating for schema gap.

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?

Description clearly states it calculates heating/cooling loads for multi-zone homes with detailed zone-by-zone analysis, distinguishing from siblings like calculate_heat_pump_sizing by specifying multi-zone focus.

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?

Provides detailed zone specification instructions but lacks explicit guidance on when to use this tool versus siblings or prerequisites (e.g., require construction details).

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