Skip to main content
Glama

Stratalize Intelligence

Get Construction Cost Benchmark

get_construction_cost_benchmark
Read-only

Construction cost benchmarks — hard cost per SF by building type and region, soft cost ratios, contingency standards, and live material cost escalation signals. Sources: NAHB, Turner Building Cost Index, RSMeans composites. For developers, lenders, and project owners. $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": {
      "building_type": "<building_type>"
    },
    "name": "get_construction_cost_benchmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionNo
building_typeYes
construction_classNo

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 cover read-only, open-world and non-destructive, so the description's added value is the per-call price ($0.02 USDC), the named data sources (NAHB, Turner, RSMeans), and the presence of live escalation signals — real behavioral context a caller would otherwise lack.

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?

Four short sentences, front-loaded with the coverage claim and ending with the cost signal; the audience sentence is the only mildly expendable line.

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 and zero parameter documentation, the definition should say more about what is returned (granularity, units/currency beyond per-SF, baseline vs range) and what construction_class A/B/C means; what it does cover is accurate but leaves these gaps.

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% for three parameters, so the description carries the burden; it names building type and region but adds no meaning beyond those names, and construction_class (A/B/C) is never mentioned or explained anywhere.

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 specific resource (hard cost per SF, soft cost ratios, contingency standards, escalation signals) and scopes it by building type and region, which is enough for an agent to distinguish it from siblings like get_shipping_cost_benchmark or get_ehr_cost_per_bed.

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?

It names an audience (developers, lenders, project owners), which implies the usage context, but gives no explicit when-to-use/when-not conditions and no routing to alternatives such as get_development_pro_forma_benchmark.

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