Skip to main content
Glama

get_rental_market_benchmark

Read-only

Rental market benchmarks — asking rents by unit type, live vacancy rate from FRED, rent growth trends, and rent-to-income ratios by market tier. Sources: HUD Fair Market Rents, FRED live vacancy, ApartmentList public data. For landlords, multifamily investors, and property managers. $0.02 USDC per call.

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_rental_market_benchmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
unit_typeNo
market_tierNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the readOnly/openWorld/non-destructive annotations, the description discloses upstream data sources (HUD Fair Market Rents, FRED, ApartmentList) and a per-call price of $0.02 USDC, which is genuinely useful behavioral context for an agent deciding whether to call. It omits data freshness/caching and whether the paid call is billed on failure, so it is not fully transparent.

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?

Two sentences: the first front-loads what the tool returns and its sources, the second covers audience and price. Dense but readable with no filler; the metric list is long but each item is informative.

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?

With no output schema, the description does well to enumerate returned metrics, but for a zero-required-parameter tool it should state the default scope when unit_type and market_tier are omitted, and it says nothing about response shape or granularity. Adequate for selection, incomplete for confident invocation.

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 coverage is 0%, so the description must carry the load: "asking rents by unit type" and "rent-to-income ratios by market tier" do hint at what the two parameters control. However, the meaning of the tier enum values (gateway/secondary/sunbelt) and, crucially, what happens when either optional parameter is omitted (national default? all unit types?) are never explained.

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?

"Rental market benchmarks" plus an enumeration of the concrete metrics returned (asking rents by unit type, live vacancy rate from FRED, rent growth trends, rent-to-income ratios) makes the resource and output content unambiguous. It does not explicitly distinguish itself from near neighbours like get_residential_market_benchmark or get_hud_fair_market_rent, so it stops short of a 5.

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

Usage Guidelines3/5

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

The audience line ("For landlords, multifamily investors, and property managers") implies the intended use case, but there is no explicit when-to-use, when-not-to-use, or statement of which sibling to pick for a different view of housing data. Guidance is inferable 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