Arcgis Darlington

The descriptions are unusually verbose and do try to steer callers (e.g. 'PREFER OVER', 'use entity_profile instead'), but the surface still has heavy overlap: ask_pipeworx vs ask_pipeworx_beta vs ask_pipeworx_grounded vs deep_research all answer questions, and entity_profile vs company_facts vs compare_entities vs recent_changes vs resolve_entity all target the same companies from different angles. Polymarket tools (edges, arbitrage, edge_tracker, fill_risk, kalshi_spread) are numerous and distinguishable mainly through long prose rather than clearly distinct names.

Nearly everything is lower_snake_case, with coherent family prefixes (polymarket_*, ask_pipeworx*, pipeworx_*). It is a bit mixed semantically — some names are verb_noun (validate_claim, discover_tools) while others are noun_noun (company_facts, entity_profile, resolution_audit) — but the convention is predictable enough to read.

39 tools is heavy, and the mismatch is severe: the server is named 'Arcgis Darlington' yet only search_datasets, layer_info, and query_layer relate to GIS, while the other 36 are a generic Pipeworx data/prediction-market gateway. The count is not scoped to the stated purpose.

For the apparent GIS/Darlington domain the surface is nearly empty — search, inspect schema, and query, with no feature create/update/delete, export, or map operations, so agents hit dead ends quickly. The Pipeworx half is broad but belongs to a different domain, so it does not compensate for the stated purpose.