Skip to main content
Glama
Sign In

HouseExhale

by io.github.attachmentnerd
OverviewDiscussionsAdmin

Rebates and tax credits

find_rebates
Read-only

What HouseExhale’s research found for a state (by ZIP code or state): utility and state programs that pay toward an HRV or ERV by name, other ventilation rebates, air sealing and insulation help, the state’s federal home energy rebates, state tax credits, and the status of the federal tax credits. Each with its link and date. Never promises eligibility.

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

Input Schema

NameRequiredDescriptionDefault
zipNoFive-digit ZIP code
stateNoTwo-letter US state, if no ZIP code

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover read-only safety and closed-world scope. The description adds meaningful behavioral context: results come with links and dates, and the tool never promises eligibility, which is important for an advisory research tool.

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?

The description is front-loaded with the core purpose and then enumerates result categories efficiently. It is somewhat list-heavy but every item contributes to what the agent should expect, with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only lookup tool with no output schema, the description sufficiently explains what comes back: named programs, other rebates, state and federal tax-credit status, links, and dates. The eligibility caveat completes the behavioral picture.

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%, so the ZIP and state parameters are already documented in the input schema. The description reinforces the ZIP-or-state choice but does not add format or precedence details beyond what the schema provides, so baseline 3 applies.

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: what HouseExhale’s research found for a state by ZIP or state, including named ventilation programs, insulation help, federal rebates, and tax credits. This is clearly differentiated from siblings like find_installers and check_ventilation_unit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description makes the use case clear: retrieve rebate and tax-credit research for a ZIP or state. It does not explicitly name exclusions or alternatives, but the scope is narrow enough that an agent can tell when to choose it over installer or unit-checking tools.

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