Skip to main content
Glama

Estatesales Companies

estatesales_companies
Read-onlyIdempotent

Estate-sale companies operating near a US ZIP code, as listed on EstateSales.NET: company name, business address, phone, coordinates and their EstateSales.NET page. Answers "who runs estate sales in this area", for hiring one, or for tracing which company is behind a sale found via estatesales_search.

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": {
      "postal_code": "64111"
    },
    "name": "estatesales_companies"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoOptional city name, e.g. "Kansas City"
state_codeNoOptional 2-letter state code, e.g. "MO"
postal_codeYesUS ZIP code, e.g. "64111"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds useful context beyond that: the data source is EstateSales.NET and the shape of the returned fields. It says nothing about result volume, pagination, or behavior for ZIPs with no listed companies, which is the remaining gap.

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?

A single sentence front-loads what the tool returns, followed by one short sentence of use cases and the sibling cross-reference. There is no redundancy or filler, and the return-field list earns its place by substituting for a missing output schema.

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?

For a read-only, three-parameter lookup with no output schema, the description covers source, scope, returned fields, and use cases — enough to call it correctly. It omits expectations about result count or empty-result behavior, which would help but are not blocking.

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 postal_code, city, and state_code are already documented with examples in the schema. The description reinforces that the ZIP drives proximity search but adds no format, fallback, or precedence rules beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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 resource and scope ("Estate-sale companies operating near a US ZIP code, as listed on EstateSales.NET") and enumerates the returned fields: name, address, phone, coordinates, and page URL. It explicitly differentiates from the sibling by noting it is for "tracing which company is behind a sale found via estatesales_search," so an agent can pick between the two without opening either schema.

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?

Gives three concrete use cases — answering "who runs estate sales in this area," hiring a company, or tracing a company behind a specific sale — and routes the tracing case to estatesales_search as the counterpart. It stops short of an explicit when-not-to-use or a statement of coverage limits, so it is clear context rather than full routing guidance.

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.