Skip to main content
Glama

SiteCheck Jobs & Property

Crexi commercial real estate listings from the JSON search

realestate_commercial_real_estate_listings
Read-only

Crexi commercial real estate listings (for sale and auction) from the JSON search the crexi.com site uses: listing ID, name, short description, property types, status (On-Market, Auction...), asking price (null when unpriced), square footage, brokerage, address with county and coordinates, listed/updated dates, offers-due date and URL, plus the total match count. Filter by US state, property type and keyword. Leases are not included. Related tools on this server, for a different need: realestate_commercial_property_transactions when you need recently recorded NYC real-property documents; realestate_bienici_real_estate when you need French property ads from Bien'ici for a city or area. 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

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "realestate_commercial_real_estate_listings"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoOptional keyword, e.g. a city name or 'Dollar General'
pageNoPage number from 1 (default 1)
typeNoOptional property type: Retail, Office, Industrial, Multifamily, Hospitality, Land, Mixed Use, Special Purpose, Self Storage, Senior Living, Mobile Home Park, Note/Loan, Business for Sale
limitNoResults per page, 1-60 (default 20)
stateNoOptional 2-letter US state code, e.g. TX

Output Schema

NameRequiredDescriptionDefault
pageNo
countNo
totalNo
sourceNo
filtersNo
listingsNo
checkedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnly/openWorld annotations, the description discloses that asking price is null when unpriced, that a total match count is returned, and that billing is $0.002 per successful call via x402 with failed calls free. The cost/charge model and unpriced-null semantics are exactly the kind of operational context annotations cannot carry.

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 it is, then returned fields, filters, exclusions, alternatives, and pricing in a logical order with no filler. The long enumeration of returned fields is somewhat dense, but every element still serves selection or interpretation.

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, the description need not re-explain returns, and it goes further by covering exclusions, alternatives, and payment terms. Minor residual gaps: pagination/limits behavior and result ordering aren't characterized in prose, though the schema covers the page/limit parameters.

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 all five parameters are already documented with defaults, ranges, and the property-type vocabulary. The description adds only a summary of which dimensions are filterable ('US state, property type and keyword') and no new syntax or constraint beyond the schema, so the baseline 3 applies.

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-scoped resource: Crexi commercial real estate listings (for sale and auction) drawn from the JSON search crexi.com uses. It distinguishes itself from nearby siblings both by data source and by an explicit exclusion ('Leases are not included').

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?

Gives a clear when-not ('Leases are not included') and two named alternatives with the condition that selects each: commercial_property_transactions for NYC recorded documents, bienici for French ads in a city/area. The filtering levers (state, property type, keyword) are also stated up front.

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