RentCast MCP Server

Overview Schema Source Related Servers Discussions Admin

get_property_value

Retrieve an automated property value estimate (AVM) with comparable sales. Provide the address and choose the number of comps.

Instructions

Get an automated value estimate (AVM) for a property with comparable sales.

Args: address: Full property address (e.g., "5500 Grand Lake Dr, San Antonio, TX, 78244") compCount: Number of comparable properties to include (1-25, default 10)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "address": "<address>"
    },
    "name": "get_property_value"
  }
}

Input Schema

Name	Required	Description	Default
`address`	Yes
`compCount`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 10, 2026

TDQS

A3.7/5.0

Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only states the purpose and parameter meanings, without mentioning limitations, error conditions, or any side effects. It does not explain what happens when no comparable sales are found or how the output is structured.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single purpose sentence followed by a concise 'Args:' block. It is front-loaded with the core function and includes no extraneous text.

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?

Given two parameters and no annotations, the description adequately explains the purpose and parameters. It lacks usage context such as when to prefer this over get_rent_estimate and does not mention potential failure modes, but the output schema covers return format.

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?

The input schema has no descriptions (0% coverage), but the description compensates by providing a full address example and clarifying compCount as the number of comparable properties with a range of 1-25 and a default of 10. This adds significant meaning beyond the schema's basic titles.

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 clearly states it retrieves an automated value estimate (AVM) for a property with comparable sales. It uses a specific verb and resource, distinguishing it from siblings like get_rent_estimate and get_property_record.

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 on when to use this tool versus alternatives such as get_rent_estimate or search_recent_sales. The description implies its use for AVM but does not mention exclusions or comparisons.

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

Deploy Server