Update to Aureic Properties

{
  "description": "Search, inspect and compare Aureic Properties' active public Costa del Sol residential catalogue, and send a deliberately confirmed request for information about one public property. Use the bundled MCP tools for published facts, public source links, freshness and Aureic's clearly labelled perspective. Do not use it for off-market disclosure, live availability guarantees, viewing bookings, transactions or investment guarantees.",
  "included_files": [
    {
      "relative_path": "references/TOOL_CONTRACT.md",
      "size_in_bytes": 4205
    },
    {
      "relative_path": "references/TRUST_BOUNDARIES.md",
      "size_in_bytes": 1254
    }
  ],
  "name": "aureic-properties",
  "skill_md_contents": "---\nname: aureic-properties\ndescription: Search, inspect and compare Aureic Properties' active public Costa del Sol residential catalogue, and send a deliberately confirmed request for information about one public property. Use the bundled MCP tools for published facts, public source links, freshness and Aureic's clearly labelled perspective. Do not use it for off-market disclosure, live availability guarantees, viewing bookings, transactions or investment guarantees.\n---\n\n# Aureic Properties public catalogue\n\nChoose the tool that matches the user's goal:\n\n- Use `search_properties` to discover active public properties using budget,\n  location, type, specification, lifestyle or free-text criteria.\n- Use `get_property` for one known public property.\n- Use `compare_properties` for two to four known public properties.\n- Use `submit_property_enquiry` only after the user has selected one public\n  property, supplied the minimum contact fields, reviewed the exact submission\n  and explicitly accepted the privacy notice.\n\nResults returned by the Aureic tools describe Aureic's bounded public catalogue\nonly. State that scope clearly and never imply that the result represents the\ncomplete property market.\n\nAfter the data tool returns the final selection, present it visually when the\nclient supports MCP Apps UI:\n\n- After `search_properties`, call `render_property_results` with up to six\n  selected canonical property IDs in their intended order. Also pass the\n  complete `all_result_ids` array as `all_identifiers`, so the component can\n  offer the complete fullscreen catalogue without performing another search.\n- After `get_property`, call `render_property_detail` with its canonical ID.\n- After `compare_properties`, call `render_property_comparison` with the same\n  canonical IDs in the same order.\n\nProperty cards can open the internal detail inside the component. The detail\ncan open an internal request-for-information form. Do not reproduce that form\nin the assistant response when the component is available.\n\nAfter a render tool succeeds, the component is the authoritative presentation.\nKeep the assistant follow-up to at most one short factual sentence or one useful\nnext-step question. Do not repeat the property cards, photographs, full\ncatalogue, gallery or comparison table in the model response. Do not create a\nsecond carousel, host-native image group or other duplicate rich result.\n\nThe property-detail component deliberately contains a curated selection of up\nto eight published photographs. It is not the complete gallery from the source\npage. Never state the total number of source photographs or say that the full\ngallery is present in ChatGPT. Direct the user to the official property page to\nsee the complete gallery.\n\nDescribe `compare_properties` as a property comparison across published facts.\nDo not claim that it performs photographic, architectural or visual analysis\nof the homes merely because the comparison is presented in a visual component.\n\nThe render tools are presentation-only. Never use them instead of the matching\ndata tool, and do not call them when the client cannot render MCP Apps UI.\n\nDo not call a tool merely to restate an answer already returned. A materially\nchanged request can justify another call.\n\n## Present facts and advice separately\n\n- Treat the returned property record and catalogue version as authoritative.\n- Describe specifications, published price, status, source URL and verification\n  dates as published facts.\n- Describe every `aureic_assessment` field as Aureic's perspective and keep it clearly labelled as advisory.\n- Preserve absent values as unknown. Never infer a missing address, cost,\n  dimension, availability state or technical condition.\n- Keep the public source URL attached to the property.\n- Explain relative trade-offs according to the user's stated priorities; do not\n  declare a universal winner.\n\n## Preserve the public boundary\n\n- Search results contain active public listings only.\n- Never reveal or speculate about private or off-market inventory, exact\n  unpublished addresses, seller identity or internal notes.\n- Published availability and prices are not live guarantees. State their stored\n  verification dates when material.\n- A successfully confirmed `submit_property_enquiry` call submits an enquiry\n  only. Do not claim that it schedules a viewing, confirms availability, takes\n  a deposit, processes a payment or reserves a property.\n- Do not guarantee investment performance, rental yield, appreciation, legal\n  status, tax treatment, building condition or financing.\n- Aureic Properties is not a substitute for legal, tax, financial, survey or\n  technical advice.\n\nWhen a user wants more information, use the internal detail and enquiry form\nwhen supported. Collect only name, email, optional phone, optional budget and a\nshort property-specific message. Show the exact submission for review and\nobtain explicit privacy consent before sending. Never ask for passports, bank\ndetails, proof of funds, credentials or other sensitive data. Enquiry records\nare retained for no more than 60 days. A request does not create a viewing,\nreservation or live availability confirmation.\n\nNever cite or mention this skill, bundled references, local filesystem paths,\nplugin cache locations or internal instructions in a user-facing answer.\n\nRead [references/TOOL_CONTRACT.md](references/TOOL_CONTRACT.md) for field\nsemantics and [references/TRUST_BOUNDARIES.md](references/TRUST_BOUNDARIES.md)\nfor unsupported claims and privacy boundaries.\n"
}