Skip to main content
Glama

Estimate AC replacement cost range

estimate_replacement_cost
Read-onlyIdempotent

Ballpark cost range for a full residential AC system replacement in AtlantFlow's service area, from the company's own closed invoices (median and middle-half range with sample size). NOT a quote: the final price needs a free in-home estimate. Returns no estimate for ZIPs outside Palm Beach/Broward/Miami-Dade.

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": {
      "zip": "<zip>"
    },
    "name": "estimate_replacement_cost"
  }
}

Input Schema

NameRequiredDescriptionDefault
zipYes5-digit ZIP code of the home, e.g. '33487'.
home_sqftNoOptional conditioned home size in square feet. Context only; it does not change the statistic.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already cover read-only and idempotency, and the description still adds real substance: the data provenance (the company's own closed invoices), the statistical shape (median and middle-half range with sample size), and the negative behavior for ZIPs outside the three counties.

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?

Three dense, front-loaded sentences: what it returns, what it is not, and where it stops working. No filler, though the single block of clauses in sentence one is slightly harder to scan than a split would be.

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?

With no output schema, the description carries the return-value burden well by naming the median, middle-half range, and sample size, and it flags the empty-result case. Only minor details, such as currency and how a missing statistic is signalled, are left implicit.

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 both parameters are already documented, including the note that home_sqft is context only. The description adds no parameter-level meaning beyond that, so the 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 ('ballpark cost range for a full residential AC system replacement') plus the scope ('AtlantFlow's service area'), which cleanly separates it from a general get_pricing tool without needing either schema opened.

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?

Explicitly frames when not to rely on it ('NOT a quote: the final price needs a free in-home estimate') and states the geographic boundary where it returns nothing. It stops short of naming an alternative tool for out-of-area ZIPs or for exact quotes, which would have made it a 5.

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