Skip to main content
Glama

Quote an active investor search

quote_active_investor_search
Read-onlyIdempotent

Finds who is actively buying in an area: properties in a zip, city or county owned by investors, grouped by owner when run. By default it looks for owners of 2+ properties who bought in this area in the last 12 months. Options: minPurchasesLast12Months keeps owners who bought at least N properties in the last 12 months. That count covers the owner's whole portfolio, not only this area, so it is the closest available measure of 'bought N+ here'; boughtWithinMonths keeps it to owners who bought here recently. corporateOnly keeps companies and LLCs. cashInvestorOnly keeps properties bought with cash by an absentee investor. outOfStateOnly keeps owners who live in another state. Each property record costs credits, the same as a national property search. Never spends credits: it counts the matches and prices one batch. Always quote first. Then tell the user the credit cost, the batch size and their balance after. Records this workspace already pulled in the last 24 hours are free. For large searches, prefer a smaller batch (limit) or narrower filters, such as a zip instead of a county. One run returns at most 250 records; page with offset. Quotes expire after 10 minutes. Call run_active_investor_search with the quote_id only after the user agrees to the credit cost.

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": {
      "state": "<state>"
    },
    "name": "quote_active_investor_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
zipNoFive-digit zip code. The narrowest and cheapest place filter.
cityNoCity name.
limitNoRecords to price in this batch (max 250). Leave empty to let the quote pick a safe batch size.
stateYesTwo-letter state code, e.g. TX. Required.
countyNoCounty name, without the word County.
offsetNoSkip this many matches. Use it to quote the next page.
propertyTypeNoSFR single family, MFR multifamily, CONDO, LAND, MOBILE or OTHER.
corporateOnlyNoOnly companies and LLCs.
outOfStateOnlyNoOnly owners whose mailing address is in another state.
cashInvestorOnlyNoOnly properties bought with cash by an absentee investor.
boughtWithinMonthsNoOnly properties in this area bought in the last N months. Default 12. Null means any time.
minPropertiesOwnedNoOnly owners with at least this many properties. Default 2.
minPurchasesLast12MonthsNoOnly owners who bought at least this many properties in the last 12 months, counted across their whole portfolio.

Output Schema

NameRequiredDescriptionDefault
offsetYes
balanceYes
creditsYes
quoteIdYes
runToolYes
expiresAtYes
affordableYes
freeSampleNo
suggestionsYes
balanceAfterYes
ownedInBatchYes
totalMatchesYes
recommendationYes
recordsInBatchYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / freeSample
      Added value: +{
      +  "type": "boolean"
      +}
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

The description is highly transparent about critical behaviors not in the schema or annotations, such as the cost model ('Each property record costs credits'), the fact that it 'Never spends credits,' the 10-minute quote expiry, and the limitations on batch size/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?

While the description is quite long due to the complexity of the tool, the structure is effective, grouping default settings, operational constraints, and usage instructions logically. It avoids redundant phrasing.

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?

The description is exceptionally complete. It covers input options, processing constraints (batch size, limits), financial implications (credits, expiry), and the exact mechanism for transitioning to the execution tool, making it robust for agent use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds essential context to several complex parameters, such as clarifying that 'minPurchasesLast12Months' refers to the owner's 'whole portfolio, not only this area,' which is a critical constraint not obvious from the schema alone.

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?

The description clearly states its purpose is to quote an active investor search. It differentiates itself from execution tools by explicitly stating it finds who is buying and that it is a quotation function.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It provides a mandatory, complete workflow: 'Always quote first. Then tell the user the credit cost... Call run_active_investor_search with the quote_id only after the user agrees.' This leaves zero ambiguity about the correct sequence of operations.

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