Skip to main content
Glama

Swapwire

Get home energy job costs from public program records

get_prices
Read-onlyIdempotent

Median installed cost and the middle half (25th to 75th percentile) for heat pumps, solar, battery storage and weatherization, from public rebate, loan and incentive program records in Oregon, New York, Massachusetts, Connecticut and Delaware, statewide and by county or city. Each series says what the cost includes (usually before the rebate) and whether the program is income-qualified. Loan amounts are not prices. Use it to tell a user whether a quote is in the usual range, and cite the source.

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

Input Schema

NameRequiredDescriptionDefault
jobNoWords to match in the job, e.g. "heat pump", "solar", "weatherization".
areaNoCounty or city, e.g. "Multnomah". Default: statewide series.
stateNoTwo-letter state code, e.g. "OR".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the read-only, idempotent, closed-world safety profile, so the description's job is data semantics, which it does well: provenance (public rebate/loan/incentive records), what each series includes, whether the program is income-qualified, and the explicit warning that loan amounts are not prices. It does not discuss record counts, sample-size caveats, or whether sparse regions return empty series, which would matter for interpreting results.

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?

Front-loads the metric and the covered technologies, then moves to provenance, then to the intended use. It is a dense ~90 words but nearly every clause carries information; the geographic list is the only mildly padded element.

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?

With no output schema, the description must convey what comes back, and it does: a median plus an interquartile range per series, with inclusion notes and an income-qualification flag. Combined with full schema coverage and annotations, an agent has enough to call this correctly and interpret the result.

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 coverage is 100%, so the baseline is 3, but the description adds meaning the schema lacks: the explicit list of supported states (schema has no enum) and the statewide-versus-county/city distinction that governs how 'area' resolves. That is real value beyond the parameter descriptions.

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: median installed cost plus the 25th-75th percentile for heat pumps, solar, battery storage and weatherization, drawn from public rebate/loan/incentive program records. The scope (five named states, statewide and county/city) is concrete enough to separate it from get_area_stats or the license tools without opening any schema.

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?

Gives a clear use case — judging whether a quote falls in the usual range and citing the source — plus a caution that loan amounts are not prices, which prevents a common misuse. It does not name an alternative tool or state when not to use this one, so it stops short of full routing guidance.

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