Skip to main content
Glama

CRE Intelligence

by io.github.Zwondra

generate_deal_memo

Generate a formatted CRE acquisition memo / Investment Committee memo. Automatically pulls live rates from FRED and demographics from Census Bureau to provide real market context — not guesses.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
noiYesNet Operating Income ($)
asking_priceYesAsking price ($)
property_typeYesMultifamily / Office / Retail / Industrial / Mixed-Use
property_addressYesFull property address
rent_roll_summaryNoOptional: paste output from analyze_rent_roll or flag_lease_risks
additional_contextNoAny additional deal notes, seller info, market color

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description discloses that live data is pulled from FRED and Census Bureau, adding transparency. However, it does not mention side effects like data saving or auth requirements, though for a memo generator these are likely minimal.

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?

The description is two sentences, front-loaded with purpose and followed by a key behavioral trait. Every word earns its place; no fluff.

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?

Given the complexity of 6 parameters and an output schema, the description covers the main purpose and data sources. It does not explain prerequisites like needing rent roll data, but the schema hints at optional inputs from sibling tools.

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 coverage is 100%, so baseline is 3. The description does not add meaning beyond what the schema provides, except indirectly noting that property address and type relate to data pulls from external sources.

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 clearly states it generates a formatted CRE acquisition/Investment Committee memo, which is a specific and distinct resource. It differentiates from sibling tools like analyze_rent_roll or build_dcf_model by being the final memo output.

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?

The description implies usage for memo generation but does not explicitly state when to use versus siblings. Context from sibling list helps, but no exclusions or alternative tool references are given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All CRE Intelligence toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0
Disambiguation5/5

Each tool targets a distinct resource and action: lease documents, rent rolls, DCF models, Excel export, risk flags, deal memos, market data, rates, inflation, demographics at two geographic levels, and land screening at two scales. No two tools have overlapping purposes.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case (e.g., abstract_lease, get_current_rates, screen_parcel_dd), making the tool surface predictable and easy to navigate.

Tool Count5/5

With 13 tools, the server is well-scoped for CRE investment analysis, covering lease abstraction, rent roll analysis, DCF modeling, market data, demographics, and land screening. The count is sufficient without being bloated.

Completeness5/5

The tool set covers the full lifecycle of CRE deal analysis: document parsing (lease, rent roll), financial modeling (DCF, Excel export), risk assessment (flag risks, parcel screens), market context (rates, inflation, demographics, CRE market data), and output (deal memo). No obvious gaps for the intended purpose.

Resources