RentCast MCP Server

Overview Schema Source Related Servers Discussions Admin

get_property_records

Retrieve property records by applying filters like location, price, bedrooms, and square footage to find matching real estate listings.

Instructions

Get property records with various filters. Returns a list of property records.

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

Input Schema

Name	Required	Description	Default
`zip_code`	No
`city`	No
`state`	No
`property_type`	No
`bedrooms`	No
`bathrooms`	No
`min_price`	No
`max_price`	No
`min_square_feet`	No
`max_square_feet`	No
`year_built`	No
`page`	No
`page_size`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Feb 11, 2026

TDQS

C2.4/5.0

Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It mentions 'Returns a list of property records' but doesn't describe pagination behavior (despite having page/page_size parameters), rate limits, authentication requirements, or what constitutes a 'property record'. The description doesn't contradict annotations (none exist), but fails to provide necessary operational context.

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?

The description is extremely concise with just two short sentences that get straight to the point. However, this conciseness comes at the cost of being under-specified for a tool with 13 parameters and multiple sibling alternatives. Every word earns its place, but more words would be justified.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex filtering tool with 13 parameters, no annotations, no output schema, and multiple similar siblings, the description is severely incomplete. It doesn't explain the relationship between this tool and alternatives, doesn't describe the return format beyond 'list of property records', and provides no guidance on parameter usage or filtering behavior.

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?

With 13 parameters and 0% schema description coverage, the description provides no parameter-specific information beyond 'various filters'. It doesn't explain what property types are available, format expectations for location fields, valid ranges for numeric parameters, or how filtering logic works (AND/OR combinations). The description fails to compensate for the complete lack of schema documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool 'Get property records with various filters' which provides a basic verb+resource combination, but it's vague about what 'property records' actually contain and doesn't differentiate from siblings like 'get_property_listings' or 'get_property_data'. It merely restates the tool name with slightly more detail.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided about when to use this tool versus alternatives like 'get_property_listings' or 'get_property_record_by_id'. The description mentions 'various filters' but doesn't specify which filters are available or suggest appropriate use cases, leaving the agent to guess based on parameter names alone.

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

Deploy Server