AutoPilot IT

The two tools are mostly distinct: one lists all public service families, while the other retrieves a specific service by exact or partial name. There is some overlap because listing also exposes descriptions and readiness, but the action boundaries are clear enough for an agent.

Both tools use the same apit_ prefix and a consistent verb_noun pattern: get_public_service and list_public_services. The naming is predictable and readable.

Two tools is thin for a server surface, even one focused on public service discovery. The tools are well-scoped, but the set feels minimal and may be insufficient for richer discovery workflows.

For a public read-only service discovery domain, listing services and getting a service by name covers the core lifecycle. Minor gaps exist, such as no explicit filtering by readiness or service family, but agents can work around this by listing and inspecting results.