Homesage.ai MCP

Get Square Footage by Floor

get_sqft_per_floor

Read-only

What it returns

Per-floor square-footage distribution for a US residential property, derived from a multi-stage AI analysis (photo/room detection, architectural-style inference, and multi-method validation). Returns the total square footage and a square_feet_by_floor map keyed by floor.

When to use it

Break out living area by floor for renovation, valuation, or listing copy.
Sanity-check a single total-sqft figure against a per-floor split.

Note: this is a heavy AI workflow — use a 45-second client timeout.

Costs 1 credit 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": {
      "address": "<address>"
    },
    "name": "get_sqft_per_floor"
  }
}

Input Schema

Name	Required	Description	Default
`address`	Yes	Full US property address. Example: `4411 E Hidden Oak St Springfield MO 65802`.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 3, 2026

TDQS

A4.1/5.0

Behavior5/5

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

The annotations already declare readOnlyHint, openWorldHint, and destructiveHint, so the description is not needed to establish that this is a safe read. What it adds is the operational context an agent cannot see elsewhere: a heavy AI workflow needing a 45-second client timeout and a cost of 1 credit per call, both of which materially affect call strategy.

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?

Two short headed sections plus a bolded note keep the definition front-loaded and scannable, and every sentence carries real information (return shape, use cases, timeout, cost). The markdown scaffolding is slightly heavy for a one-parameter tool, but no sentence is filler.

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?

An output schema exists, so the description only needs to orient the reader, and the 'square_feet_by_floor' keyed map plus total is enough for that. Latency and credit cost are covered, leaving only edge-case behavior (unmatched address, partial floors, non-US property) unaddressed.

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?

There is a single required parameter with 100% schema description coverage, including a concrete example address, so the schema already carries the semantics and the baseline of 3 applies. The description adds nothing about address formatting, normalization, or failure on ambiguous or non-US addresses.

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?

The description names a specific verb and resource: per-floor square-footage distribution for a US residential property, plus how it is derived (photo/room detection, style inference, multi-method validation). It is clearly a narrow report type rather than a general lookup, though it never names the sibling it differs from (e.g. get_property_info or get_full_report), so an agent must infer the boundary.

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?

A dedicated 'When to use it' block gives two concrete scenarios: per-floor breakout for renovation, valuation, or listing copy, and sanity-checking a single total-sqft figure. It lacks the paired 'when not to use' guidance and does not point to any alternative sibling, which keeps it below a 5.

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

All Homesage.ai MCP 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?