No user-submitted related servers found.
Scored across 94 tools
There are several near-duplicate clusters that will cause misselection: semantic_search and search_intelligence are explicitly the same retrieval layer with a different call shape, and save_site/list_saved_sites/set_site_alert runs in parallel to a second persistence system (save_to_shortlist/get_shortlist/set_shortlist_alert). Site scoring is spread across analyze_site, get_composite_site_score, score_facility, compare_sites, rank_sites, find_sites and site_selection_canvas, and grid work across get_grid_data, get_grid_scoreboard, get_grid_intelligence, get_iso_context and compare_isos. The lengthy 'do NOT use X, use Y' cross-references mitigate this considerably, but an agent still has to read them to avoid picking the wrong sibling.
The dominant pattern is snake_case verb_noun (get_facility, search_facilities, rank_markets, save_site, register_standing_intent), which is readable and largely predictable. But a large minority break it with noun phrases or bare verbs — ai_capacity_index, hyperscaler_deals, deal_autopsy, site_selection_canvas, grid_transition_radar, why_dchub, and the bare search/fetch pair. Conventions are mixed enough that the name alone does not reliably predict the shape of a call.
94 tools is roughly six times the top of the well-scoped range and well past any reasonable ceiling, even for a broad data-center/power domain. A large share of the surface is plumbing rather than domain capability: claim_free_key, bind_email, recover_my_key, unlock_more_data, read_inbox, report_finding, discover_tools, plan_query, execute_plan, get_agent_registry, get_backup_status, why_dchub. Several of these duplicate or shadow each other, so the count is inflated by meta-tooling rather than by distinct analytical coverage.
Coverage of the stated domain is unusually deep: site scoring, grid telemetry and headroom, interconnection queues, gas economics, permitting, tax, water, fiber, deals, news, capacity marketplace and alerting all have dedicated tools with honest coverage/caveat blocks. The visible gaps are lifecycle ones — saved sites and shortlists can be created and read but not updated or deleted (only standing intents have delete_standing_intent), and account/meta state has no cleanup path. Those are workaroundable but leave dead ends for an agent managing persistent state.