Skip to main content
Glama

Meadley Bros. property-picked mailing lists

Count matching homes

count_homes
Read-onlyIdempotent

How many households in a service area fit a contractor's trade, judged from property signals (tree canopy, slope, lot size, pool) rather than just addresses. Free, no key needed. Returns the count, the price to buy, and a link where the user can buy the list in one step.

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": {
      "radiusMiles": "<radiusMiles>",
      "trade": "<trade>"
    },
    "name": "count_homes"
  }
}

Input Schema

NameRequiredDescriptionDefault
latNoLatitude of the center of the service area (alternative to zip)
lngNoLongitude of the center of the service area (alternative to zip)
zipNoFive-digit US ZIP code at the center of the service area. Easiest way to say where. Send this, OR city and state, OR lat and lng.
cityNoCity name at the center of the service area, with state. Alternative to zip.
stateNoTwo-letter state, required with city.
tradeYesThe contractor's trade. One of: tree-services, forestry-mulching, land-services, lawn-care, landscaping, hardscaping, roofing, pest-control, pool-services. For any other home or property service use generic-other.
radiusMilesYesService radius in miles, 0.5 to 50. A typical contractor uses 15 to 25.
recipientModeNoWho the mail is addressed to. "owner_property" (default for most trades) uses the owner's name and mails it to the property. "owner" uses the owner's name and mails it to the owner's own address, which reaches absentee and out-of-state landlords. "resident" addresses Current Resident at the property. Forestry mulching and land clearing default to "owner". Leave it out unless the user says what they want.owner_property

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / recipientMode / description
      Previous value: -"Who the mail is addressed to. \"owner_property\" (default) uses the owner's name and mails it to the property. \"owner\" uses the owner's name and mails it to the owner's own address, which reaches absentee and out-of-state landlords. \"resident\" addresses Current Resident at the property. Leave it out unless the user says what they want."New value: +"Who the mail is addressed to. \"owner_property\" (default for most trades) uses the owner's name and mails it to the property. \"owner\" uses the owner's name and mails it to the owner's own address, which reaches absentee and out-of-state landlords. \"resident\" addresses Current Resident at the property. Forestry mulching and land clearing default to \"owner\". Leave it out unless the user says what they want."
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, openWorld. The description adds genuinely new context: no key required, no cost, and the three-part return (count, price, buy link). It stops short of noting rate limits or result sizing, but exceeds the annotation bar.

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 sentences, purpose front-loaded, zero filler. The property-signal clause earns its place by explaining what makes the count special. Slightly more compact phrasing could tighten the third sentence.

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 usefully discloses what comes back (count, price, purchase link). Combined with complete param documentation and clear read-only annotations, an agent has enough to call it correctly; only the inter-tool sequencing is 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 the schema already documents all 8 parameters in detail, including the recipientMode default logic. The description mentions property signals (tree canopy, slope, lot size, pool) but that describes the computation rather than adding meaning to any parameter. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb (count) and resource (households in a service area matching a contractor's trade), and clarifies the judging basis (property signals rather than just addresses). It does not explicitly name the sibling tools (preview_market, start_checkout) it relates to, so the differentiation is implied rather than stated.

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?

It signals this is a free, no-key, pre-purchase lookup ('Returns the count, the price to buy, and a link where the user can buy the list'), which hints at where it sits in the flow. But it never says when to use this versus preview_market or start_checkout, and gives no explicit exclusions or prerequisites.

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