Skip to main content
Glama

Meadley Bros. property-picked mailing lists

Start a purchase

start_checkout

Start buying a mailing list of the matching homes: owner names and mailing addresses delivered as an Excel file plus a CSV. Returns a Stripe Checkout URL; the user opens it and pays there (this tool never handles card details). Minimum 1000 addresses ($349). Needs a Meadley Bros. API key. Members create keys in Profile and billing under Advanced integrations. Only call this when the user has clearly asked to buy.

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>",
      "quantity": "<quantity>"
    },
    "name": "start_checkout"
  }
}

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.
listNameNoOptional name for the list in the user's account
quantityYesAddresses to buy, 1000 minimum, up to the count
cancelUrlNoOptional https URL if the user cancels. Defaults to the Meadley Bros. buy page.
successUrlNoOptional https URL to send the user to after paying. Defaults to the Meadley Bros. thank-you page.
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

A4.3/5.0
Behavior5/5

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

Goes well beyond the annotations: minimum 1000 addresses at $349, delivery as Excel plus CSV, payment happening off-tool at a Stripe URL so the agent never handles card details, and the API-key/Profile setup path. These are the concrete consequences (cost floor, external handoff, credentials) an agent needs before invoking a non-idempotent purchase.

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-loaded with what the user actually gets, then the payment handoff, then the constraints and the precondition. Five sentences with no filler; the key-creation detail is slightly incidental but supports the auth requirement.

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 still tells the agent what comes back (a Checkout URL plus file deliverables). For a mutating, open-world, non-idempotent tool it covers cost, credentials, payment flow, and the call precondition, so nothing needed to invoke it correctly is missing.

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 description coverage is 100%, so the baseline is 3 and the schema already documents all 12 parameters including the radius range and recipientMode enum. The description adds the one thing the schema lacks: the pricing floor tied to quantity (1000 minimum, $349), which lets the agent pre-check the request before calling.

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?

States a specific verb and resource: buying a mailing list of matching homes, delivered as Excel plus CSV, returning a Stripe Checkout URL. That is enough to distinguish it from count_homes and preview_market by implication (buying vs. counting/previewing), though neither sibling is named.

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 an explicit precondition: "Only call this when the user has clearly asked to buy," which is exactly the guard needed for a paid, non-idempotent tool. It also states the API key requirement and where to get it, but does not name preview_market or count_homes as the cheaper alternatives to try first.

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