Skip to main content
Glama

CRE Intelligence

by io.github.Zwondra

screen_parcel_dd

Pre-screen a land parcel's location for the AUTOMATABLE due-diligence red flags: FEMA flood zone and federal wetlands. Pulls live from FEMA's National Flood Hazard Layer and the US Fish & Wildlife National Wetlands Inventory.

Use this to kill obviously-bad parcels (flood zone, wetlands) at scale BEFORE spending time on manual due diligence.

IMPORTANT: Checks flood + wetlands only. It does NOT check legal ACCESS (landlocked — the #1 land deal-killer), title/liens, or zoning — those stay MANUAL, per-parcel checks via county records. A clean screen here is necessary, NOT sufficient.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latYesParcel latitude (decimal degrees)
lngYesParcel longitude (decimal degrees)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

A4.6/5.0
Behavior5/5

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

No annotations are provided, so the description carries the full burden. It transparently discloses the data sources (FEMA NFHL and USFWS NWI), the limited scope (flood + wetlands only), and the implications of the check. There are no contradictions or missing behavioral cues.

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?

The description is well-structured with a clear purpose statement, usage instructions, and important caveats. It is front-loaded and each sentence adds value. Slightly verbose with emphasis (all-caps) but not detrimental.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given that an output schema exists (stated), the description covers all necessary context: inputs, data sources, scope, limitations, and usage guidance. It is sufficiently complete for an agent to understand the tool's role in the workflow.

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?

The input schema has 100% description coverage (lat, lng with 'decimal degrees'). The description adds context that these are parcel coordinates but does not provide additional constraints or format details beyond the schema. Baseline 3 is appropriate.

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 the tool's purpose: 'Pre-screen a land parcel's location for the AUTOMATABLE due-diligence red flags: FEMA flood zone and federal wetlands.' It uses a specific verb ('pre-screen') and identifies the exact resource (land parcel) and checks. It also differentiates from sibling tool 'screen_land_market' by focusing on flood/wetlands due diligence.

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

Usage Guidelines5/5

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

Explicit usage guidance is provided: 'Use this to kill obviously-bad parcels at scale BEFORE spending time on manual due diligence.' It also clearly states what the tool does NOT cover (legal access, title/liens, zoning) and emphasizes that a clean screen is necessary but not sufficient.

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