Skip to main content
Glama

Monthly rent trend for a zip

rent_trend
Read-onlyIdempotent

Which way is rent moving in this zip code? Monthly median-rent history with home values, the direction of movement, and the zip's national and state rank for 3-month rent growth. Updated monthly.

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": {
      "zip": "<zip>"
    },
    "name": "rent_trend"
  }
}

Input Schema

NameRequiredDescriptionDefault
zipYes5-digit US zip code.
monthsNoHistory window in months.

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 readOnly/idempotent/closed-world, so the description is free to focus on content, and it does: it enumerates the return payload (median rent history, home values, direction, ranks) and discloses the monthly refresh cadence, which is freshness information an agent cannot get from annotations or schema. It stops short of noting history depth limits or data latency.

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?

Three short sentences, front-loaded with the core question and then the payload; no filler. Slightly fragmented phrasing ('the direction of movement, and the zip's national and state rank'), but every clause carries information.

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?

With no output schema, the description usefully compensates by naming the returned fields and the update cadence. What's missing is modest: how the months parameter changes the response, and whether ranks are among all zips or peers.

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 100% and both parameters (zip pattern, months with min 2/max 24/default 12) are fully documented there. The description adds no meaning about the months window or what the default returns, so it sits at the baseline.

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?

States a specific resource (monthly median-rent history for a single zip) plus the derived outputs: home values, direction of movement, and national/state rank for 3-month growth. This makes it distinguishable from compare_zips and get_zip_market in practice, though neither sibling is named explicitly.

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 opening question ('Which way is rent moving in this zip code?') implies the use case but gives no explicit when-to-use/when-not guidance. It never mentions compare_zips as the alternative for cross-zip comparison or get_zip_market for broader market data, so routing is left to inference.

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