Skip to main content
Glama

get_property_operating_benchmark

Read-only

Property operating benchmarks — OpEx per SF, NOI margins, and occupancy rates by property type. Sources: BOMA Experience Exchange, IREM Income/Expense Analysis, NCREIF. For asset managers, property managers, and acquisition underwriters. $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": {
      "property_type": "<property_type>"
    },
    "name": "get_property_operating_benchmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
market_tierNo
property_typeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered; the description adds genuinely new behavior information: the upstream data provenance (BOMA, IREM, NCREIF) and the per-call cost of $0.02 USDC, which matters for an agent deciding whether to invoke a paid tool. It omits any note on return format or coverage lag, keeping it short of a 5.

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?

Tight, front-loaded teletype fragments: metrics first, then sources, then audience, then price. Every sentence carries information, though the dash-fragment style reads more like a listing than a definition and could use one clause on how results are shaped.

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?

Given only two params and no output schema, the description does well to enumerate the returned metrics, sources, and cost. The notable gap is the unexplained market_tier parameter and no indication of granularity (per-market? per-year?) for the returned figures.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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. It only implies that property_type slices the results and never mentions market_tier at all, leaving the gateway/secondary/tertiary segmenting dimension — and whether it is required or defaulted — entirely to the enum values.

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?

Names the resource (property operating benchmarks), the exact metrics returned (OpEx per SF, NOI margins, occupancy rates), and the slicing dimension (property type), which cleanly separates it from siblings like get_property_tax_benchmark or get_cap_rate_benchmark.

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?

Audience targeting ('For asset managers, property managers, and acquisition underwriters') implies when the tool is relevant, but there is no explicit when-to-use/when-not-to-use rule and no named alternative among the many benchmark siblings. Usage is inferred 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