Skip to main content
Glama

SENTINEL Washington Real Estate

Recorded sale history for one property

wa_sale_history
Read-only

Read recorded sale dates and prices for one exact King, Pierce or Snohomish County parcel, from the county assessor's own published sale records (up to the last three years). Each record gives the parcel count, the county's market-validity code and whether it can serve as a comparable sale; multi-parcel, nominal and unverified prices are flagged, not hidden. No buyer, seller or owner names. Use address or county plus parcelId. A miss is not an answer and is not charged; missing records do not prove that no sale occurred, and a sale price is not a current value. The result includes an 'attributions' array (upstream source lines and the NWMLS/DOR/county non-affiliation line) and a professional-advice disclaimer — pass both through to end users.

Input Schema

NameRequiredDescriptionDefault
cityNo
daysNo
limitNo
countyNo
addressNo
zipCodeNo
parcelIdNo

Output Schema

NameRequiredDescriptionDefault
statusYes
recordsNo
has_moreNo
propertyYes
warningsNo
disclaimerNoNot legal, tax, or financial advice. Verify with licensed professionals and source records.
fetched_atNo
window_endYes
attributionsNo
window_startYes
source_coveragesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint=false; the description adds substantial behavior the agent could not otherwise know: a three-year lookback ceiling, that multi-parcel, nominal and unverified prices are flagged rather than suppressed, that misses are free, and that results carry an 'attributions' array and disclaimer that must be passed through. That is real operational context beyond the annotation profile.

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?

Purpose and geographic scope are front-loaded, followed by record contents, caveats and the pass-through obligation in a logical order. Dense but each sentence carries distinct information; the attributions/disclaimer sentence is long but operationally necessary.

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 lookup with an output schema, the description covers source, recency window, record contents, null-result semantics and end-user obligations well. The remaining gap is the undocumented optional filters and their default limits, which an agent would need for anything beyond the basic two call patterns.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden, yet it only explains address/county/parcelId and their relationship. Four of seven parameters (city, zipCode, days, limit) are never mentioned, and the 1,095-day default / 50-record limit bounds are left entirely to the schema. It compensates for the critical anyOf input modes but not for the rest.

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 and resource ('Read recorded sale dates and prices') scoped to 'one exact King, Pierce or Snohomish County parcel' from a named source. This clearly separates it from siblings like wa_property_changes, wa_comps and wa_property_lookup without any schema inspection.

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 explicit invocation modes ('Use address or county plus parcelId') and rules out ownership use ('No buyer, seller or owner names') plus warns that a miss is not proof of no sale. It stops short of naming an alternative sibling (e.g. wa_comps for comparable-sale analysis), so the routing guidance is clear but not fully comparative.

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.