Turn a US address or parcel number into an interactive 3D flyover listing in about a minute.
Scored across 3 tools
Each tool has a distinct purpose: creating a 3D listing, retrieving an existing listing, and getting pricing information. No overlap or ambiguity.
All tools follow a consistent verb_noun pattern (create_3d_listing, get_listing, get_pricing), making it easy to predict functionality.
Three tools is appropriate for a focused service covering creation, retrieval, and pricing without unnecessary complexity.
The core workflow of creating and retrieving listings plus pricing is covered, but missing update/delete functionality for listing management is a minor gap.
Build a cinematic, interactive 3D flyover listing of a real property from a street address (or a parcel/APN number) — with the parcel boundary drawn on the terrain. Takes about a minute. Returns a free watermarked preview link the user can open on any phone, plus the link to unlock the branded version (call get_pricing for what each plan includes). Use this for raw land, acreage, odd lots, waterfront and new-construction dirt — anywhere a flat satellite photo undersells the property.
| Name | Required | Description | Default |
|---|---|---|---|
| apn | No | Parcel number / APN, e.g. "07-11-31-7016-0RP0B-0030". Requires state and county. Florida resolves instantly and free. | |
| state | No | Two-letter state code — required when using apn. | |
| county | No | County name — required when using apn. | |
| address | No | Full street address, e.g. "123 Main St, Palm Coast, FL 32137". Works nationwide. Use this unless the user only has a parcel number. | |
| asking_price | No | Optional asking price in dollars. When given, it floats on the 3D view — this is what makes buyers stop scrolling. |
Look up a ParcelLaunch listing that was already created, by its listing id. Returns the address, whether the parcel boundary was found, the 3D render status, the shareable links, and whether the lot holds LIVE (the clean 3D link buyers explore, given as live_url). A lot without LIVE shares a watermarked 3D preview. A ParcelLaunch sample lot (such as f2c2bcc732) answers sample: true and no asking_price: it is a sample listing, not for sale.
| Name | Required | Description | Default |
|---|---|---|---|
| listing_id | Yes | The listing id returned by create_3d_listing (e.g. "f2c2bcc732"). |
Current ParcelLaunch pricing and what each plan includes. Free to call — use it to answer any question about cost before recommending a plan.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full transparency burden. It discloses 'Free to call' (no cost, likely no rate limits) and describes the tool's output (pricing and plan inclusions). This is adequate for a read-only tool with no parameters and no side effects.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description consists of two concise, front-loaded sentences. The first sentence states the core purpose, and the second provides usage guidance. Every word adds value with no redundancy or fluff.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple tool with no parameters and no output schema, the description fully explains what the tool does and when to use it. It covers the key return content (pricing and plan inclusions) and adds a usage hint. No additional information is necessary for an AI agent to use this tool correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, so the baseline is 4. The description adds no parameter information because none is needed; it simply states the purpose. Schema coverage is 100% (empty schema), so no additional value is required.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool returns 'Current ParcelLaunch pricing and what each plan includes.' It uses the specific verb-phrase 'get' implicitly and distinguishes from sibling tools 'create_3d_listing' and 'get_listing' by focusing solely on pricing and plan details.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly guides usage with 'Free to call — use it to answer any question about cost before recommending a plan.' This provides clear context and a recommended use case, though it does not explicitly mention when not to use it or alternative tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
get_listing1 field changedInput schema / properties / listing_id / descriptionPrevious value: -"The listing id returned by create_3d_listing (e.g. \"7291ac49b3\")."New value: +"The listing id returned by create_3d_listing (e.g. \"f2c2bcc732\")."create_3d_listingget_listingget_pricingEnhance, virtually stage and turn real estate listing photos into video with AI.
U.S. real-estate data: property records, AVM value + rent estimates, sale/rental listings.
Property intelligence: 180M+ US parcels — lookup, search, owners, hazards, permits, deeds.
Real estate data for AI agents: US parcel boundaries (tiles), owners, sale history, permits, hail.
Add one secure layer between your agents and this server.
