Skip to main content
Glama
Sign In

Xome

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Xome Property Detail

xome_property_detail
Read-onlyIdempotent

Full detail for one Xome foreclosure/REO auction listing: property facts, the exact sale event (date + courthouse venue address), sale terms (buyer's premium, financing, payment method), and the bid/sale PRICE with an explicit status label. VERIFIED live 2026-09-13: for upcoming sales this is an opening-bid estimate or starting bid (often unset); for a closed-but-undecided sale it is the highest bid received (NOT a completed sale); for a confirmed completed sale (including "Sold to Bank", where the foreclosing lender took the property back) it is the real realized sale price. Every response says explicitly which case applies — never treat estimated_or_starting_bid or high_bid_received as a sale price. Get url from xome_search. A high bid on an open sale is served through a 5-minute result cache and can be up to five minutes old. Sourced from the listing's own page (schema.org JSON-LD plus its embedded Next.js auction-state data).

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "https://www.xome.com/auctions/975-e-democracy-ave-fresno-ca-93720-181526576"
    },
    "name": "xome_property_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesFull xome.com listing url from xome_search, e.g. "https://www.xome.com/auctions/975-e-democracy-ave-fresno-ca-93720-181526576"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Adds substantial context beyond the readOnly/idempotent annotations: a 5-minute result cache that can serve a high bid up to five minutes stale, the provenance of the data (schema.org JSON-LD plus embedded Next.js auction-state), and a four-case price semantics model. That staleness and interpretation disclosure is exactly the kind of behavioral detail annotations cannot express.

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 tool returns, then the price semantics, then operational caveats. The price paragraph is long but each case (estimated/starting bid, high bid, realized sale, Sold to Bank) earns its place given the price-misread risk. Minor room to tighten the repeated emphasis on not treating bid labels as sale prices.

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?

No output schema exists, and the description fully compensates by naming the returned sections and the explicit status labeling. The one remaining agent need — how to obtain a valid url — is answered inline.

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 coverage is 100% and there is only one param, so the schema already defines the url format. The description still adds value by constraining provenance (the url must come from xome_search rather than being constructed), which the schema text does not enforce.

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+resource ("Full detail for one Xome foreclosure/REO auction listing") and enumerates the exact returned sections: property facts, sale event with courthouse venue, sale terms, and price with status label. Positions itself clearly against the sibling xome_search as the detail follow-up.

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?

"Get url from xome_search" gives the explicit prerequisite and predecessor tool, which is the only real routing decision here. It does not add a when-not-to-use clause, but no competing sibling exists for single-listing detail, so the guidance is effectively complete.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Xome toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources