analyze_site
ActiveTool of cloud.dchub/mcp-server
Use when a user has ONE specific lat/lon (a parcel, a candidate site) and wants the full multi-factor data-center suitability read in one call. Example: "Score this Phoenix parcel for a 100MW build — power, gas, fiber, market & risk." — analyze_site lat=33.45 lon=-112.07 capacity_mw=100 state=AZ. Params: lat (-90 to 90, required unless candidate_id), lon (-180 to 180, required unless candidate_id), candidate_id (a cand_… from get_refined_queue — resolves coordinates from the frozen mint and ignores lat/lon), capacity_mw (target load in MW, e.g. 50-500), state (2-letter US, optional — improves the tax-incentive/context lookup), include_grid/include_risk/include_fiber (booleans, default true). Returns (full, paid): {overall_score (aka composite_score, 0-100 composite — for the integrity-first version that never imputes a missing factor, use get_composite_site_score), interpretation (verdict string, e.g. "Excellent site"), scores{power_infrastructure, gas_pipeline_access, fiber_connectivity, market_conditions, risk_resilience — each 0-100}, nearby{substations_50km, power_plants_80km, gas_pipelines_50km, facilities_100km, fiber_carriers_in_state, generation_capacity_mw, total_capacity_mw}, power_cost{industrial_cents_kwh, commercial_cents_kwh, period, basis}, fiber{connectivity_score, nearest_carrier_km, near_net_bucket, top_carriers[], single_carrier_risk}, location, citation}. FREE tier returns a REAL, citable HEADLINE — composite_score + verdict + the single top limiting factor (the lowest sub-score) + citation; the full per-factor breakdown, nearby infrastructure, power cost, fiber carriers, and the branded Site Analysis PDF (generate_site_analysis) are Pro. For dedicated water / disaster / climate / tax reads use get_water_risk / get_disaster_risk / get_climate_intel / get_tax_incentives. Do NOT use to compare 2+ sites (use compare_sites) or to find sites that match a target (use find_alternatives).
Parameters schema
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"lat": {
"type": "number",
"description": "Site latitude in decimal degrees (-90 to 90; required unless candidate_id given), e.g. 33.45"
},
"lng": {
"type": "number",
"description": "Alias for lon — either name works"
},
"lon": {
"type": "number",
"description": "Site longitude in decimal degrees (-180 to 180; required unless candidate_id given), e.g. -112.07"
},
"state": {
"type": "string",
"description": "US state abbreviation (optional) — improves the tax-incentive lookup, e.g. AZ"
},
"latitude": {
"type": "number",
"description": "Alias for lat — either name works"
},
"longitude": {
"type": "number",
"description": "Alias for lon — either name works"
},
"capacity_mw": {
"type": "number",
"description": "Target power load for the build in megawatts (MW), e.g. 100 (typical 50-500)"
},
"candidate_id": {
"type": "string",
"description": "PREFERRED for queue survivors: a cand_… id from get_refined_queue — coordinates come from the FROZEN mint (lat/lon args are ignored; zero transcription drift; expired ids fail closed with candidate_expired). See dchub.cloud/docs/candidate-lifecycle"
},
"include_grid": {
"type": "boolean",
"description": "Include grid-headroom / substation analysis (default true)"
},
"include_risk": {
"type": "boolean",
"description": "Include water/drought/climate risk analysis (default true)"
},
"include_fiber": {
"type": "boolean",
"description": "Include fiber-connectivity analysis (default true)"
}
}
}No endpoints wrapped at confidence ≥ 0.70.
Parent server
cloud.dchub/mcp-server
https://github.com/azmartone67/dchub-backend
1/7 registries