Scored across 6 tools
Each tool targets a distinct data type: search for places, place details, reviews for a place, reviews by a contributor, photos, and posts. There is no ambiguity between them, even though search and place details both return place info — search is for discovery, place details is for a specific known place.
All tool names follow a consistent pattern: hasdata_google_maps_<resource>_get<Action> (or performMapSearch for search). The resource is always a clear noun (search, place, reviews, contributor_reviews, photos, posts), and the action verb is consistent (get) or explicit (performMapSearch). This is highly predictable.
Six tools is a well-scoped count for a Google Maps data extraction server. Each tool covers a distinct endpoint needed for local business intelligence, and none are redundant or trivial. This is within the ideal range and feels complete for the stated purpose.
The tool set covers the core lifecycle of Google Maps data: search for places, fetch details for a place, retrieve reviews (both for a place and by a contributor), get photos, and get posts/updates. This is a comprehensive read-only surface for building location-aware agents, lead generation, and reputation management, with no obvious gaps.