Skip to main content
Glama

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.8/5.0
Behavior4/5

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

Annotations already establish that this is a safe read-only, open-world lookup with no destructive behavior. Beyond that, the description adds meaningful operational context: data sources (NAHB, ULI, industry composite) and a per-call price of $0.02 USDC. It does not describe freshness, units, or response format, but the added cost and source information is substantive for a simple benchmark lookup.

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?

Three short sentences carry the metric list, audience, sources, and price with no filler. The domain and metrics are front-loaded, so an agent can scan the important information immediately.

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 low-complexity benchmark lookup, the description covers what is returned, who it is for, where it comes from, and what it costs. It is still somewhat incomplete on output units and does not explain market_tier, but it provides enough context to select and invoke the tool for its primary use case.

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?

With 0% schema description coverage, the description needs to explain both parameters. It only says the benchmarks are segmented 'by product type,' which loosely maps to product_type, and it never mentions the optional market_tier parameter or defines gateway/secondary/tertiary. The enum values are somewhat self-explanatory, but the description does not compensate for the missing schema documentation.

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 clearly identifies the resource as development pro forma benchmarks and lists the specific metrics covered: yield on cost, profit-on-cost, construction-to-perm spread, and return hurdles. It distinguishes itself from other benchmark siblings through the real-estate-development domain, though it does not explicitly name an alternative or use a direct retrieval verb.

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?

It gives clear audience context: developers underwriting new projects and lenders sizing construction loans. That makes the intended use case explicit, but it does not state exclusions or explain when to choose this over adjacent benchmarks such as construction cost or cap rate.

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