Skip to main content
Glama

A-du: ADU rentals, plans and rules

Estimate market rent for an ADU

get_rent_estimate
Read-onlyIdempotent

Estimate the monthly market rent for an ADU or small unit at a specific address, with a low and high range, from a long-term rent valuation model over nearby comparables or from HUD Small Area Fair Market Rents and asking rents A-du collected. Use when a landlord asks what to charge, or a renter asks whether a listed rent is fair. Requires a street address plus bedrooms, bathrooms and square feet. The default property type is a detached ADU. This is an automated estimate, not an appraisal, and it does not account for the unit's condition or finishes. Example: {"address": "123 Elm St, Long Beach, CA 90802", "bedrooms": 1, "bathrooms": 1, "square_feet": 520}.

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>",
      "bedrooms": "<bedrooms>",
      "bathrooms": "<bathrooms>",
      "square_feet": "<square_feet>"
    },
    "name": "get_rent_estimate"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesFull street address including city and state.
bedroomsYes
bathroomsYes
square_feetYes
property_typeNoUnit type. Detached, attached and internal ADUs are valued as multi-family; a front house as single family.single_family_adu_detached

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description still adds real behavioral context: the estimate comes from a comparables-based valuation model or HUD Small Area Fair Market Rents, returns a low/high range, and explicitly excludes condition and finishes ('not an appraisal'). That is meaningful added value, though no latency, coverage limits, or fallback behavior is disclosed.

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?

Purpose and scope are front-loaded, followed by usage triggers, caveats, and a compact example call. A few sentences are redundant with structured data (the required-field list and the default property type), but nothing is padded or vague.

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?

There is no output schema, and the description compensates by describing the returned low/high range and its sources, plus the key accuracy caveat about condition and finishes. For a five-parameter read-only estimation tool this is nearly complete; only the numeric parameter units remain unaddressed.

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 description coverage is only 40%, with bedrooms, bathrooms and square_feet undocumented in the schema. The description restates which four inputs are required and notes the default property type is a detached ADU, but adds no unit conventions or bounds for the numeric fields, so it only partially compensates for the coverage gap.

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 opens with a specific verb and resource: 'Estimate the monthly market rent for an ADU or small unit at a specific address,' and even names the output shape (a low and high range). It never names a sibling such as get_rental or search_rentals, so the agent must infer the boundary between estimating a rent and fetching an existing listing.

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?

It gives concrete when-to-use triggers ('a landlord asks what to charge, or a renter asks whether a listed rent is fair') and states the required inputs up front. It stops short of explicit when-not-to-use guidance or naming an alternative tool for cases where the caller actually wants an existing listing's rent.

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