Skip to main content
Glama
tandat8503

Rentcast MCP Server

by tandat8503

get_property_details

Retrieve comprehensive property information using a property ID to support accurate valuation and market analysis.

Instructions

Get detailed property information and prepare parameters for property value estimation

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesProperty or listing ID for detailed information

Implementation Reference

  • Main handler function for get_property_details tool. Fetches property details by ID, formats the information, and prepares parameters for related valuation and rent estimation tools.
    async (params) => {
      try {
        // This tool helps prepare property data for other tools
        const result = await rentcastAPI.getProperty(params.id);
    
        if (!result.success) {
          return createErrorResponse("Error getting property details", result.error);
        }
    
        const property = result.data as any;
        if (!property) {
          return createErrorResponse("No property details found");
        }
        
    
    
        // Format property details
        const propertyInfo = formatPropertyInfo(property);
        
        // Prepare parameters for property value estimation
        const valueEstimationParams = createPropertyValueParams(property);
        const rentEstimationParams = createRentEstimationParams(property);
        
        const additionalInfo = `\n\nšŸ’” **Copy these values to the get_property_value tool to get an automated valuation estimate!**\n\n` +
          `šŸ  **Rent Estimation Parameters:**\n` +
          `${extractPropertyParams(property)}\n\n` +
          `šŸ’” **Copy these values to the get_rent_estimates tool to get rent estimates!**`;
    
        const resultText = propertyInfo + valueEstimationParams + additionalInfo;
        return createSuccessResponse(resultText);
    
            } catch (error) {
          return createErrorResponse("Failed to get property details", error instanceof Error ? error.message : 'Unknown error');
        }
    }
  • Zod schema defining the input parameters for the get_property_details tool, requiring a property ID.
    export const PropertyDetailSchema = z.object({
      id: z.string().describe("Property or listing ID for detailed information"),
    });
  • src/index.ts:692-731 (registration)
    MCP server tool registration for get_property_details, including name, description, input schema, and handler function.
    server.tool(
      "get_property_details",
      "Get detailed property information and prepare parameters for property value estimation",
      PropertyDetailSchema.shape,
      async (params) => {
        try {
          // This tool helps prepare property data for other tools
          const result = await rentcastAPI.getProperty(params.id);
    
          if (!result.success) {
            return createErrorResponse("Error getting property details", result.error);
          }
    
          const property = result.data as any;
          if (!property) {
            return createErrorResponse("No property details found");
          }
          
    
    
          // Format property details
          const propertyInfo = formatPropertyInfo(property);
          
          // Prepare parameters for property value estimation
          const valueEstimationParams = createPropertyValueParams(property);
          const rentEstimationParams = createRentEstimationParams(property);
          
          const additionalInfo = `\n\nšŸ’” **Copy these values to the get_property_value tool to get an automated valuation estimate!**\n\n` +
            `šŸ  **Rent Estimation Parameters:**\n` +
            `${extractPropertyParams(property)}\n\n` +
            `šŸ’” **Copy these values to the get_rent_estimates tool to get rent estimates!**`;
    
          const resultText = propertyInfo + valueEstimationParams + additionalInfo;
          return createSuccessResponse(resultText);
    
              } catch (error) {
            return createErrorResponse("Failed to get property details", error instanceof Error ? error.message : 'Unknown error');
          }
      }
    );
  • Helper method in RentcastAPI service that calls the Rentcast /properties/{id} endpoint to retrieve detailed property information.
    async getProperty(id: string): Promise<ApiCallResult> {
      const result = await this.makeRequest<RentcastProperty>(
        `/properties/${id}`,
      );
      return result;
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'prepare parameters for property value estimation,' hinting at a preparatory or intermediate step, but fails to clarify if this is a read-only operation, what data it returns (e.g., structured details vs. raw parameters), or any limitations (e.g., rate limits, authentication needs). This leaves significant gaps for a tool with potential downstream effects.

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, efficient sentence that front-loads the core action ('Get detailed property information') and adds secondary purpose ('prepare parameters for property value estimation') without redundancy. Every word earns its place, making it highly concise and well-structured.

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

Completeness3/5

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

Given the tool's moderate complexity (single parameter, no output schema, no annotations), the description is minimally adequate. It states the purpose clearly but lacks behavioral details (e.g., return format, error handling) and usage context, which are needed for full completeness. Without an output schema, it should ideally hint at what 'detailed property information' entails, but it doesn't, leaving room for improvement.

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?

The schema description coverage is 100%, with the single parameter 'id' well-documented as 'Property or listing ID for detailed information.' The description adds no additional parameter semantics beyond this, such as format examples or constraints, so it meets the baseline score of 3 where the schema does the heavy lifting.

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

Purpose4/5

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

The description clearly states the tool's purpose with specific verbs ('Get detailed property information' and 'prepare parameters for property value estimation'), which distinguishes it from siblings like 'get_property_value' (which likely returns the value itself) and 'search_properties' (which likely returns a list). However, it doesn't explicitly differentiate from all siblings (e.g., 'get_rental_listings' might also provide property details), keeping it from a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, exclusions, or compare to siblings like 'get_property_value' (for actual value estimation) or 'search_properties' (for broader searches), leaving the agent to infer usage from context alone.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tandat8503/mcp_rentcast'

If you have feedback or need assistance with the MCP directory API, please join our Discord server