Skip to main content
Glama

get_reit_benchmark

Read-only

REIT valuation and performance benchmarks — FFO multiples, AFFO multiples, dividend yields, NAV premium/discount, and total returns by property sector. Source: NAREIT public monthly data. For REIT analysts, portfolio managers, and IR teams. Free.

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_sector": "<property_sector>"
    },
    "name": "get_reit_benchmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
property_sectorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful context beyond that: the data source (NAREIT public monthly data) conveys cadence and provenance, and 'Free' signals no auth/quota gate. It stops short of stating snapshot freshness, lag, or return shape.

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?

Four short front-loaded fragments: what it returns, which metrics, the data source, the audience, and cost. Every clause carries information and none is padding, which suits a read-only benchmark lookup.

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 single-parameter, read-only lookup with no output schema, the definition supplies everything needed to call it correctly: the metric set effectively previews the return payload, and the source establishes cadence. Missing only granularity details such as whether returns are per-sector time series or a single latest snapshot.

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

Parameters4/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 the parameter meaning; 'by property sector' does explain that the single required argument is a sector selector determining which benchmark slice is returned. The enum values are largely self-explanatory, though it does not clarify that 'all_equity' is an aggregate rather than a single property type.

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 specific resource (REIT valuation and performance benchmarks) and enumerates the exact metrics covered: FFO multiples, AFFO multiples, dividend yields, NAV premium/discount, and total returns. The volatile-domain qualifier 'by property sector' plus 'REIT' cleanly separates it from the many other benchmark siblings such as get_cap_rate_benchmark or get_cre_debt_benchmark without needing to name them.

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?

States an audience ('REIT analysts, portfolio managers, and IR teams'), which implies the usage context, but gives no explicit when-to-use/when-not or routing to an alternative tool. An agent can infer this is the REIT-specific benchmark but receives no guidance on choosing it over other valuation benchmarks for edge cases.

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