Skip to main content
Glama

get_cre_acquisition_diligence

Read-only

Use when underwriting a CRE acquisition and need one signed composite across cap rates, CRE debt, operating costs, property tax, debt-stress, and location climate risk score. Degrades per-section on source_unavailable. Inputs location and state (required); optional asset_class, property_type, market_tier. $3.00 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": {
      "location": "<location>",
      "state": "<state>"
    },
    "name": "get_cre_acquisition_diligence"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateYes
locationYes
asset_classNo
market_tierNo
property_typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

With readOnlyHint and non-destructive already declared, the description still adds real behavioral context: partial results are returned per-section when a source is unavailable ("degrades per-section on source_unavailable"), and the cost is stated at $3.00 USDC per call. That degradation and pricing information is materially useful for an agent deciding whether to call. The nature of "signed" and the response shape are left unexplained.

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 dense sentences with the use case front-loaded and no filler; each sentence carries distinct information (purpose, degradation behavior, inputs, price). The input enumeration sentence is the weakest, since it mostly duplicates schema metadata.

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?

For a multi-source composite with no output schema, the description should explain what the returned composite looks like (scale, direction of "signed", section structure). It covers failure behavior and price but leaves the return value underspecified, and the asset_class/property_type ambiguity is unresolved.

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 largely doesn't - it only restates that location/state are required and the other three are optional, which the schema already marks. More importantly, asset_class and property_type have heavily overlapping enums (multifamily, industrial, retail_strip, self_storage appear in both) and the description never explains how the two differ or how to choose, which is a likely invocation error.

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 deliverable - one signed composite score spanning cap rates, CRE debt, operating costs, property tax, debt-stress, and climate risk - which is concrete enough to distinguish it from single-dimension benchmark siblings like get_cap_rate_benchmark or get_climate_risk_score. It stops short of explicitly naming those siblings as the alternative, but the composite-vs-single framing is clear.

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 a clear triggering context ("when underwriting a CRE acquisition") rather than a vague purpose, so an agent knows the decision phase this belongs to. It does not state when NOT to use it or point to the per-dimension tools as the alternative for narrower needs.

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