Skip to main content
Glama

Tennessee Property Records

Search ownership records / transfers

search_ownership_records
Read-only

Ownership records (one row per owner per parcel) for an owner, owner_key, mailing address or pin, or every transfer recorded in one county over up to 3 calendar months. Filter by price, current vs former, and address; sort by date or price. Use it for questions like 'who bought in Davidson in March 2024 over $1M'.

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": "search_ownership_records"
  }
}

Input Schema

NameRequiredDescriptionDefault
pinNoParcel pin(s), comma-separated.
sortNodate_desc (default), date_asc, price_desc.
limitNoResults per page, 1–200 (default varies by tool).
ownerNoOwner name words.
countyNoCounty (one, for date searches).
cursorNonext_cursor from the previous page, to fetch the next page.
addressNoProperty address words (filters the other results).
currentNotrue = current owners only, false = former owners only.
date_toNoAcquired on or before, YYYY-MM-DD.
mailingNoExact mailing address.
date_fromNoAcquired on or after, YYYY-MM-DD.
max_priceNoMaximum recorded price.
min_priceNoMinimum recorded price.
owner_keyNoExact owner_key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavior — result cardinality (one row per owner per parcel) and the hard constraint that date-range searches cover a single county and at most 3 calendar months — but says nothing about pagination behavior or how a limit default is chosen ('default varies by tool' is only in the schema).

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, front-loaded with the resource and lookup modes, and the closing example question earns its place by pinning down the intended query. The first sentence is heavily clause-stacked, which costs some readability but no words are wasted.

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 14-parameter, zero-required search tool with an output schema absent but annotations present, the description covers the key search modes and the non-obvious county/date-window restriction. Pagination and limit-default behavior are left to the schema, which is acceptable, but an explicit note that results page via cursor would close the remaining 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 description coverage is 100%, so the schema already defines every parameter and the baseline is 3. The description adds real meaning for one interaction only — county is mandatory and single-valued for date searches — while the remaining filter/sort parameters are merely restated, not elaborated beyond the schema.

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 names the resource and its grain precisely ('ownership records (one row per owner per parcel)') and enumerates the lookup keys: owner, owner_key, mailing address, pin, or a county transfer sweep. The filter and sort options plus a concrete example question make it distinguishable from siblings such as search_owners or owner_portfolio 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?

It gives clear when-to-use context via the county-plus-date-range path ('every transfer recorded in one county over up to 3 calendar months') and a sample question that shows the intended query shape. It stops short of explicit exclusions, e.g. when to prefer search_owners or property_at instead, so the agent must infer the boundary.

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