Skip to main content
Glama

Top rental markets leaderboard

top_markets
Read-onlyIdempotent

Which US rental markets look strongest right now? National (or single-state) leaderboard: zips with the highest estimated cap-rate bands among markets with population of 10,000+ and complete rent, vacancy, and home-value data. Cap rates are a modeled band.

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": "top_markets"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
stateNoOptional 2-letter US state code, e.g. GA. Omit for nationwide.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, so the description does not need to repeat safety details. It adds valuable behavioral context by disclosing the ranking methodology, the population/data-completeness filters, and that cap rates are a modeled band rather than observed values.

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 two tight sentences with the core purpose front-loaded as a question. Every clause adds useful scope or methodology information, and there is no wasted text.

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?

For a simple two-parameter read-only ranking tool, the description covers the ranking basis, universe filters, and modeled nature of cap rates. It does not explain the return shape in detail, but the leaderboard framing and lack of an output schema make the omission minor.

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 50%: the state parameter is documented in the schema, and the description reinforces its meaning by noting national versus single-state scope. The limit parameter has constraints in the schema but no semantic explanation in either the schema or the description, so the description does not fully compensate for the gap.

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

Purpose5/5

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

The description states a specific resource (a leaderboard of zips) and a precise ranking criterion (highest estimated cap-rate bands), along with the inclusion universe (population 10,000+, complete rent/vacancy/home-value data). This is clearly distinct from siblings like search_markets, compare_zips, or get_zip_market.

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 US rental markets look strongest right now?') implies the intended use case, and the national-or-single-state scope is clear. However, it does not explicitly say when to prefer this over search_markets or compare_zips, nor does it state exclusions or prerequisites.

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