Skip to main content
Glama

CRE Intelligence

by io.github.Zwondra

get_market_demographics

Get Census Bureau demographics for any US property address. Returns median income, population, employment rate, housing vacancy, median rents, and education levels for the census tract.

This is address-specific data from the actual Census tract — not estimates. Claude cannot access this without the MCP. For 1/3/5-mile trade-area rings, use get_radius_demographics instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressYesFull US property address (e.g. "1234 Main St, Charlotte, NC 28202")

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

A4.3/5.0
Behavior4/5

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

No annotations provided, so description carries burden. It notes the data is 'address-specific from actual Census tract — not estimates', indicating precision and reliability. Also mentions that Claude cannot access without MCP, setting expectations. No negative behavioral traits omitted.

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?

Five sentences, each valuable: action, return fields, non-estimate claim, access limitation, alternative tool. No wasted words.

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 simple one-param tool with output schema, description covers action, return fields, data source, and provides alternative. Adequate for agent to invoke correctly.

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% with description for 'address'. The tool description adds no extra info about the parameter beyond what schema provides ('Full US property address'). Baseline of 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?

Description clearly states 'Get Census Bureau demographics for any US property address' and lists returned fields. It explicitly distinguishes from sibling get_radius_demographics by advising to use that for trade-area rings.

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?

Provides explicit alternative tool (get_radius_demographics) for different use cases, and states the tool's limitation ('Claude cannot access this without MCP'). Lacks explicit 'when to use' statement, but purpose implies it.

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