USDV Capital — Your Real Estate CFO

markets-stats

Read-onlyIdempotent

Get detailed real estate market statistics for a specific location including demographics, housing data, Zillow market trends, investment metrics, and lending availability. Data from Census ACS 2023 and Zillow Feb 2026. USDV Capital — Your Real Estate CFO.

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": "markets-stats"
  }
}

Input Schema

Name	Required	Description	Default
`state`	Yes	State name or 2-letter code
`location`	Yes	City, county, or state name

Schema Changelog

Changes observed during successful MCP inspections.

First observedApr 13, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already mark it as read-only and idempotent. The description adds useful context about data sources (Census ACS 2023, Zillow Feb 2026) and the breadth of data, but does not disclose output format or any potential limitations. This goes beyond annotations but not significantly.

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 short and front-loaded with the primary purpose. The first sentence is dense with useful information. The branding at the end (USDV Capital — Your Real Estate CFO) is non-essential but does not significantly hurt conciseness.

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 read-only market statistics tool with two simple parameters, the description covers what data will be returned, data sources, and location scope. It lacks mention of output format, but the absence of an output schema makes this less critical. The level of detail is adequate for an agent to understand the tool's function.

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% for the two parameters, and descriptions exist for both. The tool description does not add extra meaning beyond the schema, so it meets the baseline but does not elevate it.

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 gets detailed real estate market statistics for a specific location, listing specific data categories. This distinguishes it from sibling tools like markets-compare (comparison) and markets-screener (screening) by emphasizing location-specific stats.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives like markets-search or markets-compare. The description does not mention exclusions or alternatives, so the agent receives no proactive selection help.

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

All USDV Capital — Your Real Estate CFO tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?