Skip to main content
Glama

Stratalize Intelligence

Get Development Pro Forma Benchmark

get_development_pro_forma_benchmark
Read-only

Development pro forma benchmarks — yield on cost, profit-on-cost, construction-to-perm spread, and return hurdles by product type. For developers underwriting new projects and lenders sizing construction loans. Sources: NAHB, ULI, industry composite. $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": {
      "product_type": "<product_type>"
    },
    "name": "get_development_pro_forma_benchmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
market_tierNo
product_typeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/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 non-redundant context: the upstream sources (NAHB, ULI, industry composite) and a per-call price of $0.02 USDC, which matters for an agent deciding whether to spend a call. It does not address latency, caching, or data vintage.

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?

Three short sentences, front-loaded with the metrics list, then audience, then provenance and cost. Every sentence carries information, though the audience sentence could have been merged with a routing hint to be more economical.

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, the description usefully enumerates what metrics come back, which covers the return-value gap reasonably. However, for a two-parameter benchmark tool it leaves the market_tier dimension and the data vintage (how current the benchmarks are) unexplained, so an agent still has open questions before calling.

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 carries the full burden of explaining parameters, and it only partially does so via the phrase "by product type." The optional market_tier parameter (gateway/secondary/tertiary) is never mentioned, nor is the behavior when it is omitted, leaving the agent to guess at defaults and segmentation.

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 names the resource and enumerates the specific metrics returned — yield on cost, profit-on-cost, construction-to-perm spread, return hurdles — segmented by product type. This clearly separates it from adjacent siblings such as get_cap_rate_benchmark or get_construction_cost_benchmark, which cover different metric families.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"For developers underwriting new projects and lenders sizing construction loans" gives a concrete use context that tells an agent which task this serves. It stops short of naming alternatives or stating when NOT to use it (e.g., for stabilized-asset cap rates), so it falls short of a 5.

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