compare_data_centers
ChatGPTUse this when the user wants to compare 2 to 6 facilities side by side, using facility_id values from search_data_centers. Returns normalized known facts, known fit issues, and unknowns for each facility, plus a requirement_fit section when project requirements are supplied. It does not pick a winner and does not confirm availability or pricing.
estimate_colocation_cost
ChatGPTUse this when the user asks what colocation might cost in a U.S. market for a given power requirement (kW, or racks with kW per rack). Returns a budgetary range per kW per month and an estimated monthly range from Colocation Scout budgetary guidance based on actual quotes it has received, with assumptions, confidence, and the variables that move price. This is budgetary guidance, not a provider quote. When no approved pricing data applies, it returns an insufficient-data result instead of a range.
get_data_center_details
ChatGPTUse this when the user wants more detail about one facility returned by search_data_centers. Returns the known location, campus status, building size, stated power and density capability, connectivity, certifications, which fields are unknown, and how current the data is. Does not confirm current availability or pricing.
request_sourcing
ChatGPTUse this only when the user accepts the sourcing offer or explicitly asks Colocation Scout to check current availability, obtain quotes or current pricing, help engage providers, or contact them. Creates a sourcing request in Colocation Scout's business system and shares the user's business contact details and requirements with the Colocation Scout team, who may contact the user. Requires consent (consent_to_contact: true): normally the user sends the show_sourcing_form form; in chat, the user sent their details after being shown the disclosure. Collect only name, company, work email and an optional phone; take market, power and go-live from the conversation and do not ask for other details; never collect passwords, payment card, financial account, or government ID information. Do not call this just because the user searched for facilities. Repeating an identical request returns the original reference instead of creating a duplicate. If the user asks for this without a sourcing_offer in the conversation, ask for name, company and work email (phone optional) and say that by sending them they agree that Colocation Scout will contact you about this request. They may be paid by the provider you choose. That never raises your price: providers can't offer a lower price for going direct. Matching is entirely based on your requirements.
search_data_centers
ChatGPTUse this when the user wants to find colocation data center facilities that may fit a deployment in a U.S. market, state, or radius around a market, optionally with power (kW), rack, density, connectivity, certification, redundancy, or cooling requirements. Searches the Colocation Scout facility database and returns likely-fit facilities with a match score, match reasons, possible gaps, and the facts that still need confirmation. Results identify likely-fit facilities from known facility characteristics. They do not represent confirmed current capacity. Many facilities have limited power and connectivity data; unknown values are returned as null. Live availability and pricing require provider confirmation.
show_sourcing_form
ChatGPTUse this when the user accepts the sourcing offer or asks Colocation Scout to check current availability or pricing. Shows a short form, prefilled with the market, power and go-live from the conversation (and name, company, work email or phone only if the user already gave them), where the user enters their name, company and work email and sends the request themselves. The brokerage disclosure is shown above the send button. Showing the form sends nothing. Do not ask for contact details in chat when this form is available.
