Skip to main content
Glama

Homesage.ai MCP

Property Condition from Photos

property_condition_custom_photos
Read-only

What it returns

An overall property-condition rating and confidence score, combining a database lookup with AI vision analysis of property photos you supply. Providing images yields a more accurate assessment than the address-only property-condition endpoint.

Performance

Image analysis is slow — use a 60-second client timeout and cache responses.

Input modes

  • Address only — database lookup (same as property-condition).

  • Image URLs — pass image_urls, comma-separated (up to 25).

  • File upload — POST multipart/form-data with an images field (up to 15 files).

  • Combined — address + images for the most accurate result.

Costs 3 credits per call.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "property_condition_custom_photos"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressNoProperty address. Either `address` or `image_urls` must be provided.
image_urlsNoComma-separated image URLs (up to 25). URL-based images work with a standard JSON request; file uploads require a multipart request.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/non-destructive, and the description adds operationally important traits beyond them: slow image analysis, a recommended 60-second client timeout, and a caching recommendation. The 3-credit cost also discloses a side effect not captured by annotations. Missing only detail on failure behavior or what happens when neither input is supplied.

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?

Markdown headers make it skimmable and the return value is front-loaded ahead of performance and input details. Minor redundancy: the address-only mode is described twice (under What it returns and again under Input modes), and the credit cost sits at the tail rather than with the other operational warnings.

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 an output schema exists, the description need only cover invocation behavior, and it covers modes, upload mechanics, latency expectations, caching, and cost — everything an agent needs to call it correctly. Nothing material for a zero-required-parameter, two-field tool is absent.

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% and both parameters already document the 25-URL limit and the multipart requirement for uploads, so the description largely restates structured information. Its marginal additions — the combined address+images mode and the 15-file upload cap — are useful but modest against a schema that already does the heavy lifting.

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?

Opens with a concrete statement of output — an overall property-condition rating plus confidence score — and names the mechanism (database lookup combined with AI vision analysis). It explicitly contrasts itself with the address-only `property-condition` endpoint, so an agent can pick between this and the `get_property_condition` sibling without inspecting either schema.

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?

Enumerates four distinct input modes (address only, image URLs, file upload, combined) and states that images yield a more accurate assessment, which is exactly the when-to-use guidance an agent needs. It also flags cost (3 credits) and the alternative address-only endpoint, leaving little to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources