Generate Site Analysis
generate_site_analysisTurn any lat/lon into a branded Site Analysis PDF, evaluating power, transmission, gas, water, air, fiber, latency, market, and tax. Get a shareable client-ready report link.
Instructions
Use when a user wants a SHAREABLE, branded multi-page Site Analysis PDF for ONE lat/lon (a powered-land parcel, a candidate campus) — the polished client deliverable, not just a score. Example: "Make the Site Analysis PDF for this Carrier Mills parcel, 150 MW, for TON Infrastructure." — generate_site_analysis lat=37.694 lon=-88.65 capacity_mw=150 prepared_for="TON Infrastructure" prepared_by="Martone Advisors". Params: lat (-90 to 90, required), lon (-180 to 180, required), capacity_mw (target load MW, e.g. 50-500), prepared_for (client name on the cover), prepared_by (your firm — brands the report; defaults to DC Hub), latency_target (optional metro override; default = nearest real carrier hotel). Returns: {survey:{verdict, power/transmission, gas, water, air-permitting, fiber carriers, latency-to-nearest-carrier-hotel, market, tax}, pdf_report_url}. pdf_report_url is a ready-to-open link to download the branded 5-page PDF — no login needed, valid ~7 days; hand it to your human. For just the numeric suitability score (no PDF), use analyze_site instead.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| lat | No | Site latitude in decimal degrees (-90 to 90, required), e.g. 37.694 | |
| lng | No | Alias for lon — either name works | |
| lon | No | Site longitude in decimal degrees (-180 to 180, required), e.g. -88.65 | |
| latitude | No | Alias for lat — either name works | |
| use_case | No | Optional workload descriptor to tailor the report, e.g. "AI training campus" | |
| longitude | No | Alias for lon — either name works | |
| capacity_mw | No | Target power load for the build in megawatts (MW), e.g. 150 (typical 50-500) | |
| prepared_by | No | Your firm name that brands the report; defaults to DC Hub, e.g. "Martone Advisors" | |
| prepared_for | No | Client name printed on the report cover, e.g. "TON Infrastructure" | |
| latency_target | No | Optional metro to measure latency against; default = nearest real carrier hotel |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| quota | No | Caller quota state (remaining calls, tier) when available. | |
| _entity | No | Payload class discriminator (e.g. facility|market|iso_grid|queue_results|deal|report|response) — branch on this before parsing the rest. | |
| citation | No | Machine-readable citation: how to attribute DC Hub (dchub.cloud) for this payload. Normally an OBJECT {source, url, license, cite_as, retrieved_at}; a bare string is accepted and carries the attribution line itself. | |
| provenance | No | Collection-level provenance block: {source, method, as_of, verification_counts, cite_url_template, license, cite_as}. Quote the verification level when citing. | |
| _front_door | No | In-band front-door hint (first workflow-entry tool of a session): call plan_query(intent) first for the ordered multi-step plan. | |
| _return_loop | No | Suggested next-session delta call (get_changes since=24h) so you pull only what changed. | |
| site_evaluation_handoff | No | Pre-built follow-up calls (analyze_site / get_water_risk args) when the payload carries coordinates — an array of {tool, parameters, why} entries. |