Skip to main content
Glama

Homes listed for sale by owner on ForSaleByOwner.com

realestate_forsalebyowner
Read-only

Homes listed for sale by owner (FSBO) on ForSaleByOwner.com for a US city: the first 20 listings with address, ZIP, coordinates, asking price (USD), property type, the owner's description (beds, baths, size and features as written by the seller), photo and listing link, plus the total number of FSBO listings in the city. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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>",
      "city": "<city>"
    },
    "name": "realestate_forsalebyowner"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityYesCity name, e.g. Austin
limitNoListings, 1 to 20 (default 20)
stateYesTwo-letter US state code, e.g. TX
maxPriceNoOnly listings at or below this price (USD)

Output Schema

NameRequiredDescriptionDefault
cityNo
countNo
stateNo
sourceNo
resultsNo
checkedAtNo
totalListingsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the readOnly/openWorld annotations, the description discloses the most decision-relevant behavior: the result is capped at the first 20 listings, a total count is returned, and each successful call costs $0.002 via x402 with failures uncharged. It does not explain the ordering or selection rule for those first 20 listings, which is the remaining behavioral gap.

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 purpose, then scope, then return contents, then cost. The enumeration of returned fields is dense but readable; the pricing sentence is separate and clearly delineated. Minor density, no real waste.

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 an output schema present, listing return fields is redundant but harmless, and payment/total-count details fill the gaps that matter. The one thing an agent still cannot learn is result ordering or how the 20-listing cap is chosen when a city has more listings.

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 coverage is 100% and the schema already documents city, state, limit and maxPrice, so the schema carries the parameter burden. The description only reinforces the city/US-state framing and does not add format or constraint detail beyond it, which is the expected baseline.

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 (homes listed for sale by owner on ForSaleByOwner.com) and pins the scope to a US city, which cleanly separates it from a sibling like realestate_virtual_staging. An agent knows exactly what dataset this returns.

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 implied by the scope statement (US city, FSBO listings only), but there is no explicit when-to-use guidance, no exclusions such as rentals or agent-listed homes, and no named alternative for the agent to prefer. The agent must infer the selection conditions.

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