Skip to main content
Glama

Stratalize Intelligence

Get Cre Acquisition Diligence

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

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely new operational context: per-section graceful degradation when a source is unavailable, and a stated $3.00 USDC cost per call, both of which affect whether and how an agent should invoke it. A fuller disclosure would say what the signed composite contains or how degradation is surfaced to the caller.

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 dense sentences with no waste: trigger condition first, then degradation behavior, then inputs and pricing. Every sentence contributes information an agent needs before calling, and the most decision-relevant content is front-loaded.

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 composite tool with 5 parameters at 0% schema description coverage and no output schema, the description covers trigger, degradation behavior, inputs, and cost — enough to call it correctly. The remaining gap is the unresolved asset_class vs property_type distinction and the vague 'signed composite' phrasing, though no output schema means return-format detail is not strictly required.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/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 burden, and it does list all five inputs with the required/optional split. However, it adds no meaning beyond the schema — notably it never clarifies the overlap between asset_class and property_type, whose enums share values like multifamily and industrial, leaving a real ambiguity unresolved. Baseline 3 for a low-coverage schema with partial compensation.

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?

Names a concrete deliverable — 'one signed composite across cap rates, CRE debt, operating costs, property tax, debt-stress, and location climate risk score' — which is clearly an aggregation tool rather than a single-section benchmark. That framing implicitly separates it from siblings like get_cap_rate_benchmark and get_climate_risk_score, but no sibling is named explicitly, so the differentiation is inferred rather than stated.

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?

States a clear usage context: 'Use when underwriting a CRE acquisition and need one signed composite' across multiple sections. It does not say when to prefer the single-section sibling tools instead (e.g., when only the cap rate is needed), so the agent must infer the boundary. Still, the triggering condition is explicit and actionable.

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