Skip to main content
Glama

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

B3/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the underlying sources (NAHB, Turner Building Cost Index, RSMeans composites) signal data provenance and freshness ambiguity, and the '$0.02 USDC per call' price discloses a real invocation cost. It omits any statement about defaults for optional parameters or how current the escalation signals are.

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?

Dense and front-loaded: the payload contents come first, then sources, then audience, then price — a sensible ordering with no filler sentences. It reads as catalog copy more than operational instruction, but every sentence carries distinct information.

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 0% parameter coverage, the description should do more work than it does: it never indicates the shape of a response (e.g., a single per-SF point estimate vs. a range with breakdowns) or how the escalation signals are expressed. Given the tool's simplicity (three flat enum parameters, one required), what is present is broadly adequate, but the unexplained construction_class and absent return format leave real 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%, so the description must carry parameter meaning, and it only partially does: 'by building type and region' maps loosely onto two of the three parameters without stating defaults or whether region can be omitted. The third parameter, construction_class with enum A/B/C, is never mentioned and its meaning (likely construction quality/finish class) is not inferable from the enum values alone.

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 concrete resource and its contents — hard cost per SF by building type and region, soft cost ratios, contingency standards, material escalation — so an agent knows exactly what data class this tool returns. It does not explicitly distinguish itself from near-neighbors like get_development_pro_forma_benchmark or get_shipping_cost_benchmark, relying on the 'construction' domain label to separate it.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no stated prerequisites, and no named alternative for adjacent needs (e.g., a full pro forma vs. a raw cost benchmark). The only contextual statement is an audience list ('developers, lenders, and project owners'), which describes who the data is for rather than the conditions under which this tool should be selected.

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