Every tool has a clearly distinct purpose targeting specific resources and actions in the tracking/scanning domain. For example, create_scan configures scans, trigger_scan_run executes them, get_scan_results retrieves keyword data, and get_scan_run fetches run details—no overlap or ambiguity exists.

All tools follow a consistent verb_noun pattern with snake_case, such as create_scan, get_credits, list_projects, and trigger_scan_run. This uniformity makes the toolset predictable and easy for agents to navigate without confusion.

With 8 tools, the server is well-scoped for managing scans, projects, and runs in a tracking system. Each tool earns its place by covering distinct operations like creation, listing, triggering, and retrieval, avoiding bloat or thin coverage.

The toolset provides strong CRUD/lifecycle coverage for scans and projects, including create, list, get, and trigger operations. A minor gap exists in update/delete functionality for scans or projects, but agents can work around this for core workflows.