Skip to main content
Glama
Sign In

HouseExhale

by io.github.attachmentnerd
OverviewDiscussionsAdmin

HRV and ERV units to ask about

units_to_ask_about
Read-only

Lists up to three reviewed HRV/ERV families whose HVI-certified airflow covers what the household’s bedrooms need at night, with margin: units to ask installers about, never a single pick or a recommendation, and never paid placement. Also returns the night airflow target and how it was worked out.

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": {
      "bedrooms": "<bedrooms>"
    },
    "name": "units_to_ask_about"
  }
}

Input Schema

NameRequiredDescriptionDefault
zipNoFive-digit ZIP code (used for the state if state is missing)
stateNoTwo-letter US state, e.g. "CO"
bedroomsYesEvery bedroom, with how many people sleep in each
floorAreaSqftNoConditioned floor area in square feet, for the daytime code rate

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare a read-only, closed-world, non-destructive operation, so the safety profile is covered. The description adds genuinely non-obvious behavior: a hard cap of three results, the 'never paid placement' independence guarantee, and that the night airflow target plus its derivation are returned — details invisible in the schema or annotations.

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 sentences, front-loaded with the capability and followed by the disclaimers; nothing is wasteful. Slightly dense with stacked qualifiers ('with margin', 'never a single pick or a recommendation, and never paid placement'), but each clause carries real routing or trust value.

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?

No output schema exists, and the description compensates by disclosing the shape of the result (up to three families plus the night airflow target and its derivation). Combined with annotations covering the safety profile, this is nearly complete; only the zip/state fallback relationship is left entirely to the schema.

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 description coverage is 100%, so all four parameters (zip, state, bedrooms with nested sleepers/name, floorAreaSqft) are already documented in the schema. The description references the nighttime bedroom requirement, loosely tying to the bedrooms array, but does not explain the night-versus-daytime split that floorAreaSqft feeds — so it stays at the baseline of 3.

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?

States a specific verb and resource — 'Lists up to three reviewed HRV/ERV families' — plus the qualifying criterion (HVI-certified airflow covering nighttime bedroom needs with margin). It also preemptively distinguishes itself from a decision tool ('never a single pick or a recommendation'), which separates it from siblings like find_installers and find_rebates.

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 makes the usage context clear (sizing units for a household's bedrooms at night) and sets a strong boundary that it is an exploration aid, not a recommendation. However, it never names an alternative tool or states when a user should go to find_installers or check_ventilation_unit instead, so routing must be inferred from the sibling names.

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

All HouseExhale toolsInspect
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.

Resources