Skip to main content
Glama

Stratalize Intelligence

Get Reit Benchmark

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

B3.4/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 meaningful context beyond that: data provenance (NAREIT public monthly data), update cadence, and cost (free). It does not describe latency, historical depth, or how the sector argument changes coverage, so it only partially extends the annotation picture.

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?

Two compact sentences front-load the metric coverage, then provenance. Most sentences carry information, though the audience sentence ('For REIT analysts, portfolio managers, and IR teams. Free.') is closer to marketing than to invocation guidance and could be trimmed without loss.

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?

There is no output schema, so the description must convey the return shape; it does so at the metric-name level, which is helpful. It omits time period, units, and whether returns are trailing or forward, leaving an agent unable to describe results precisely. Adequate but with clear gaps for a data-retrieval tool.

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 would need to explain the single parameter, which it does not. The parameter is a self-explanatory sector enum with clear literal values, but ambiguous members such as 'all_equity' versus 'diversified' are not clarified anywhere. The metric list indirectly signals what the sector slices, which keeps this at a baseline 3.

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?

The description names a specific resource (REIT valuation and performance benchmarks) and enumerates the concrete metrics returned: FFO multiples, AFFO multiples, dividend yields, NAV premium/discount, and total returns. It is unambiguous as to what data is fetched. It does not differentiate itself from the many sibling benchmark tools beyond the domain word 'REIT,' but the resource noun and metric list are distinctive enough.

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?

Usage context is only implied via the audience statement ('For REIT analysts, portfolio managers, and IR teams'), which suggests when the tool is relevant but gives no explicit when/when-not conditions and no alternatives. There is no guidance on choosing between sectors vs. 'all_equity', or on when a different benchmark tool would be more appropriate.

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