Casafari Location Lookup

Each tool targets a clearly different concern: account_status reports quota/plan, locations_get retrieves a single record by id, and locations_search resolves names/postcodes to ids. There is no realistic way to confuse them, and descriptions reinforce the boundary (search produces ids, get consumes them).

locations_get and locations_search follow a clean resource_action snake_case pattern, so the two core tools read predictably as a pair. account_status deviates slightly (no verb, different prefix), but it is a distinct meta concern and remains readable.

Three tools is on the lean side but defensible for a narrowly scoped lookup service: quota check, resolution, and retrieval. Each tool earns its place, though the surface is thin enough that a fourth operation would not feel like bloat.

Search plus get-by-id covers the core read path, and account_status prevents dead-end token failures. However, locations_get only reports whether children exist without any way to list them, and there is no coordinate/reverse-geocode lookup, forcing agents to guess names or use external tools for common location tasks.