FedWatch — Federal Funding & Lien Watcher

property_search

Search Maricopa County Assessor parcel records (GIS Parcels layer) by APN, situs-address fragment, or subdivision/address keyword. Parcel identity, situs address, sale date/price, deed and subdivision only — owner name and mailing address exist in the layer and are deliberately never returned. TOOL SHAPE ONLY: recorder documents and tax delinquency are not this pack; delinquency data belongs to the liens program.

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

Input Schema

Name	Required	Description
`apn`	No	Assessor parcel number (APN or APN_DASH form)
`limit`	No	Maximum returned records (tier-capped)
`address`	No	Situs street-address fragment
`keyword`	No	Address or subdivision name fragment
`source_id`	No	Source id: maricopa_property_records (default)

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 24, 2026

TDQS

A4.1/5.0

Behavior4/5

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

No annotations exist, so the description carries the full burden, and it does disclose the non-obvious behavior that owner name and mailing address are deliberately withheld and that only a fixed field set returns. It leaves gaps on read-only confirmation, result-count/pagination behavior, and how the tier cap truncates results.

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?

Three sentences, front-loaded with the verb and resource, followed by the return-field boundary and the sibling boundary. Each sentence earns its place, though jargon like "TOOL SHAPE ONLY" costs a little clarity.

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?

With no output schema, the description usefully enumerates the returned fields (identity, situs address, sale date/price, deed, subdivision) and the deliberate omissions. Remaining gaps are the "tier-capped" limit behavior and total/count reporting, which an agent would want to know before paging.

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%, so all five parameters are already documented. The description restates the APN, address, and keyword modes and the layer context but adds no syntax, matching, or limit-cap semantics beyond what the schema says; baseline 3 applies.

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 ("Search Maricopa County Assessor parcel records (GIS Parcels layer)") plus the three lookup keys. The negative scope sentence explicitly separates it from recorder-document and delinquency tools, so an agent can place it against siblings like liens_search without opening a 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?

Clear about which identifier types to search by and explicitly routes delinquency questions away ("delinquency data belongs to the liens program"). It stops short of naming the exact sibling tool to call or stating required prerequisites, so it is strong context rather than a full when/when-not map.

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

All FedWatch — Federal Funding & Lien Watcher 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?