HeritageDeed Title Search and Property Data

check_address

Read-onlyIdempotent

Check an address BEFORE ordering (takes a few seconds). For a title search (report_type 'current_owner', the default) give state and county: it matches the address to a real parcel in the county's records. For report_type 'environmental' only the address is needed: it is matched with the US Census geocoder (any US address). status 'matched' = safe to order; 'not_found' = ask the user to correct the address; 'not_covered' = the county is not covered; 'unavailable' = the county / Census service is down right now (a title search can still be ordered and retries; an environmental order needs the geocoder, so try again later).

Input Schema

Name	Required	Default
`state`	No
`county`	No
`address`	Yes
`report_type`	No	current_owner

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 20, 2026

addedInput schema / properties / county / default
```
Added value: +""
```

addedInput schema / properties / report_type

Added value: +{
+  "default": "current_owner",
+  "title": "Report Type",
+  "type": "string"
+}

addedInput schema / properties / state / default
```
Added value: +""
```

changedInput schema / required

Previous value: -[
-  "address",
-  "state",
-  "county"
-]New value: +[
+  "address"
+]

First observedOct 7, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds substantial behavior: expected latency ('takes a few seconds'), the meaning of all four status outcomes, and degraded-mode guidance that differs per report_type when the backend is down. This is context the annotations cannot express.

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 the key 'BEFORE ordering' instruction and latency note, and every clause carries information. It is dense as a single paragraph, but the status enumeration earns its space and nothing is 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?

There is no output schema, and the description compensates by fully enumerating the return statuses and their required follow-up actions. For a validation tool with 4 params and no structured output, an agent has everything needed to call it and interpret results.

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

Parameters5/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, and it does: it documents all four parameters including their conditional requirements and the two recognized report_type values with 'current_owner' as default. It converts bare parameter names into actionable semantics.

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 ('Check an address') and frames it as a pre-order validation step, which cleanly separates it from siblings like order_title_search and check_coverage. The report_type branching makes the scope unambiguous.

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?

Explicitly says to run it 'BEFORE ordering' and gives the exact conditions that determine the call shape: state+county required for report_type 'current_owner', address alone for 'environmental'. It also routes the agent on what to do for each status, including correcting the address on 'not_found' and retrying later on 'unavailable'.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All HeritageDeed Title Search and Property Data tools Inspect

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

Need Help?