Skip to main content
Glama

Estatesales Sale

estatesales_sale
Read-onlyIdempotent

One EstateSales.NET sale in full, by sale ID: name, description, terms, sale type, every scheduled date/time, coordinates, picture count, and the company or seller running it with their phone and page. The street address is included only once EstateSales.NET has published it, estate sales are usually at a private home and the site holds the address back until shortly before the sale.

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": {
      "sale_id": 5065767
    },
    "name": "estatesales_sale"
  }
}

Input Schema

NameRequiredDescriptionDefault
sale_idYesEstateSales.NET sale ID, e.g. 5065767 (the `id` from estatesales_search)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, so the safety profile is covered. The description adds real context beyond them: the street address appears only once EstateSales.NET publishes it, with the reason given (private-home sales, address held back until shortly before the sale). That pre-empts an agent misreading an absent address as an error.

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?

Two sentences, with the field inventory front-loaded before the address caveat. The second sentence is longer than it needs to be — 'estate sales are usually at a private home and the site holds the address back' could be tightened — but it carries genuine information rather than filler.

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?

There is no output schema, so the description properly takes on the return-value burden by listing what comes back, and it explains the one field that may legitimately be missing. What it lacks is guidance on how the sale ID is obtained and what errors occur for an unknown ID, which for a simple single-parameter read is a modest gap.

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 single parameter already documents its format and origin ('the `id` from estatesales_search'), so the baseline is 3. The description's 'by sale ID' restates the schema without adding new syntax, range, or failure-mode detail.

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 opens with a specific verb and resource — 'One EstateSales.NET sale in full, by sale ID' — and then enumerates the fields returned (name, description, terms, sale type, dates, coordinates, picture count, company). That is enough for an agent to tell this apart from the search sibling, which returns listings rather than one complete sale.

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 rather than stated: 'by sale ID' signals a detail lookup that follows a search, and the schema note points at estatesales_search as the source of the ID. There is no explicit when-to-use/when-not statement and no mention of how this differs from estatesales_companies beyond the resource names.

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.