deliverable-tracker

Most tools target distinct resources and actions cleanly: schedule creation/deletion/listing/getting/documenting, deliverable add/delete/status, licensing, and payload generation. There is minor overlap between delivery_schedule_get and late_report, since both surface late deliverables, but their descriptions make the intended use distinguishable.

The dominant pattern is object_action in snake_case: deliverable_add, delivery_schedule_create, license_activate. A few outliers like late_report and milestone_payload are noun phrases rather than verb-led actions, but the naming stays readable and mostly predictable.

Twelve tools is a well-scoped count for a deliverable-tracking server. Each tool supports a real part of the workflow: schedule management, deliverable lifecycle, reporting, client-facing documents, license handling, and integration payloads.

The core lifecycle is well covered: schedules can be created, deleted, listed, retrieved, and documented, while deliverables can be added, progressed, and deleted when still planned. There are minor gaps such as no explicit schedule update/close tool and limited edit capability, but the refusal guidance to add corrected deliverables provides a workable path.