Skip to main content
Glama

get_cap_rate_benchmark

Read-only

Commercial real estate cap rate benchmarks by asset class, market tier, and geography. Source: CBRE and JLL quarterly cap rate surveys. Used by CRE acquisition teams, asset managers, and real estate CFOs for property pricing and portfolio valuation. $0.02 USDC per call.

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": {
      "asset_class": "<asset_class>"
    },
    "name": "get_cap_rate_benchmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionNo
asset_classYes
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?

Annotations already cover the safety profile (readOnly, openWorld, non-destructive), and the description adds two pieces of genuinely new behavioral data: the upstream source (CBRE and JLL quarterly cap rate surveys, which implies quarterly refresh cadence) and the cost of $0.02 USDC per call. What it omits is the shape and granularity of the returned benchmark.

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?

Four short sentences, front-loaded with the resource and dimensions, followed by source, audience, and price. The audience sentence is the weakest, verging on marketing, but it does double as use-case context, so nothing is truly wasted.

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 and zero parameter descriptions, the description should say what a benchmark record looks like (a cap rate range per asset class/tier/region, and whether unspecified dimensions are returned as a breakdown or an aggregate). Coverage of source, cost, and dimensions is solid, but that return-shape gap matters for a tool an agent must invoke blind.

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 0%, so the description must carry parameter meaning, and it only partially does: 'asset class, market tier, and geography' map onto the three properties and confirm region = geography. It does not explain the tier semantics (gateway vs secondary vs tertiary), nor what happens when the optional region or market_tier are omitted.

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?

Names a specific data resource (commercial real estate cap rate benchmarks) and scopes it by the three dimensions that map to its parameters: asset class, market tier, geography. The 'cap rate' framing distinguishes it from siblings such as get_cre_debt_benchmark. No verb is stated, but the noun phrase is unambiguous for a data-retrieval tool.

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?

It gives an implied usage context by naming the audience and the job (CRE acquisition teams, asset managers, CFOs for property pricing and portfolio valuation), which tells an agent roughly when this is relevant. It does not say when to choose this over neighboring benchmark tools, nor does it set any 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