Skip to main content
Glama

Meadley Bros. property-picked mailing lists

Preview the market

preview_market
Read-onlyIdempotent

The measured count for a trade and area, plus every strategy card the trade offers (id, name, whether it is the widest) so the user can narrow by sending strategyIds, and which property signals are measured there. Needs a Meadley Bros. API key. Members create keys in Profile and billing under Advanced integrations.

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

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.
strategyIdsNoOptional card ids from a previous preview_market answer; cards OR together.
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.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuine value beyond that: it states a Meadley Bros. API key is required and tells the user where to create one, which is the main failure mode for a first call. It does not say whether previews are billed or rate-limited, so it stops short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences: what you get, how to narrow it, and the auth prerequisite. Nothing is redundant with the schema, and the auth note is placed last where it does not obstruct the core return-value description.

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 compensates by enumerating the returned payload (count, strategy cards and their fields, measured signals). Auth is disclosed, and all nine parameters are fully documented in the schema, so nothing an agent needs to call this correctly is missing.

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%, including enum explanations, radius ranges and recipientMode defaults, so the schema carries the parameter burden and baseline 3 applies. The description only adds the flow-level meaning of strategyIds (cards from a previous preview, ORed together) and echoes that result cards are what feeds it.

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 concretely enumerates what comes back (measured home count, strategy cards with id/name/widest flag, measured property signals) for a given trade and area, which is more useful than the name alone. It never states the action in a single verb+resource sentence and makes no attempt to distinguish itself from count_homes, so an agent must infer the preview-vs-count boundary.

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?

Usage is only implied: the mention of narrowing 'by sending strategyIds' and the API-key prerequisite hint at a preview-then-narrow workflow, but there is no explicit when-to-use, no when-not, and no reference to count_homes or start_checkout. The sibling relationship with start_checkout (preview then checkout) is left entirely to inference.

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