RetailIntel — Indian retail moves

Most tools occupy clearly distinct niches: entity profiles (brand_profile, get_group), trackers (get_expansion_map, get_leadership_moves), feeds (latest_moves, daily_brief), and lookup (search). The main overlap is fetch vs get_signal, which both return the full read of a move/signal, and fetch vs brand_profile/get_group for brand/theme content. Descriptions do enough work to steer selection, but the fetch/get_signal boundary is genuinely blurry.

Two conventions coexist: get_* family (get_signal, get_group, get_expansion_map, get_leadership_moves) and bare noun/verb forms (brand_profile, compare_brands, daily_brief, latest_moves, search, fetch). All snake_case and readable, but the 'get_' prefix is applied inconsistently to equivalent retrieval operations. Predictable enough to parse, not a uniform pattern.

Ten tools is well-scoped for a retail-intelligence server spanning brands, groups, cities, people, and move feeds. Each tool maps to a distinct query shape rather than a redundant variant. No filler tools and no obviously missing slot that would warrant an eleventh.

Coverage across brands, groups, cities/malls, leadership, signals, moves, and search is broad, with the daily brief adding editorial context. The notable gap is themes: they are mentioned throughout (search, compare_brands, fetch by theme:<slug>) but there is no theme_profile/get_theme equivalent to brand_profile or get_group. Agents can work around this via search+fetch, so it is a minor gap.