Skip to main content
Glama

Homesage.ai MCP

Get Short-Term Rental Analysis

get_short_term_rental
Read-only

What it returns

Projected short-term rental performance — nightly rate band, expected occupancy, monthly gross income, net of typical expense ratios. Built from STR comparables in the same micro-market.

When to use it

  • Evaluate STR opportunities for buy-and-host investors.

  • Compare LTR vs. STR income on the same property.

Pricing

5 credits.

FAQ

Does it account for local STR regulations?

No — markets with STR bans/caps may produce projections that aren't operationally achievable. Verify local rules before underwriting.

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": {
      "property_address": "<property_address>"
    },
    "name": "get_short_term_rental"
  }
}

Input Schema

NameRequiredDescriptionDefault
property_addressYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds genuinely new behavioral context: a 5-credit cost, the comparables-based derivation, and the limitation that regulatory caps can invalidate the projection. It does not cover latency, failure modes for unparseable addresses, or credit charging on failure.

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?

Markdown headers front-load the return shape and usage before the FAQ, so the highest-value information comes first. The FAQ section is a bit heavy relative to a one-parameter tool, but each block does carry real content rather than filler.

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?

An output schema exists, so the description's return-value summary is a bonus rather than a requirement, and cost plus the regulatory caveat round it out well. The remaining gap is the address input, which is the only way an agent can fail this call and is left entirely undocumented.

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?

The single required parameter, property_address, has 0% schema description coverage, and the description never mentions it at all — no statement of accepted formats, whether a standardized/validated address is required, or whether ambiguous addresses fail. The only guidance is the schema's inline example, which the agent must infer from.

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 states a specific verb and resource: projected short-term rental performance with named outputs (nightly rate band, occupancy, monthly gross income, net of expense ratios) and the data source (STR comparables in the same micro-market). It implicitly separates itself from get_long_term_rental by framing LTR-vs-STR comparison, but it never explicitly names the sibling tool to route against.

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?

Two explicit use cases are given (buy-and-host evaluation, LTR vs. STR income comparison), plus a clear when-not caveat that STR bans/caps can make projections unachievable. It stops short of naming get_long_term_rental as the alternative call for the LTR side of that comparison, so the routing is implied rather than stated.

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