Skip to main content
Glama
Sign In

Xome

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Xome Search

xome_search
Read-onlyIdempotent

Browse US residential foreclosure/bank-owned (REO)/short-sale auction listings on xome.com by state (and optional county). Returns property facts (beds/baths/sqft/year built/lot size/occupancy), sale type and auction_status/bid_deadline for every listing on the page — NOT the bid or sale price (call xome_property_detail for that plus the exact sale date and courthouse venue). Sourced from xome.com/auctions/{state}[/{county}].

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": {
      "state": "ca",
      "county": "fresno"
    },
    "name": "xome_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoResult page, starting at 1 (each page holds ~50-100 listings)
stateYesTwo-letter US state code, e.g. "ca", "tx", "fl"
countyNoOptional county name, e.g. "fresno" or "los angeles" (spaces become dashes automatically)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

With annotations already declaring read-only, open-world, idempotent, and non-destructive behavior, the description adds crucial context beyond annotations: it lists the property facts returned (beds/baths/sqft/year built/lot size/occupancy), sale type and auction_status/bid_deadline, and explicitly states what is NOT returned (bid/sale price). It also identifies the data source pattern (xome.com/auctions/{state}[/{county}]).

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?

The description is a single, dense paragraph that front-loads the core purpose, then efficiently packs in return details, exclusions, and the data source. Every sentence earns its place without redundancy or filler.

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?

Given the tool's complexity (a paginated search endpoint), the lack of an output schema, and annotations that cover safety, the description provides all necessary context: what data is returned, what is not, where it comes from, and which sibling handles the missing info. Nothing essential for correct invocation 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%, so the schema already fully documents all three parameters (page, state, county) including examples and county space-to-dash behavior. The description adds no new parameter-level semantics beyond restating that filtering is by state and optional county.

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 states a specific verb (Browse), resource (US residential foreclosure/bank-owned/REO/short-sale auction listings), and scope (by state and optional county on xome.com). It explicitly distinguishes itself from the sibling xome_property_detail by noting what it does NOT return (bid or sale price).

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?

The description clearly indicates when to use this tool: to browse listings by state (and optional county). It also names the alternative tool (xome_property_detail) for the missing information (bid/sale price, exact sale date, courthouse venue), leaving no ambiguity about which tool to choose.

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