Summarise a Depot project cache
depot_get_cache_summaryDiagnose why builds miss cache or layers may be evicted: summarizes retention policy vs current size, recent hit ratio, time saved, and plain-language observations.
Instructions
Report the health of one Depot project's layer cache: the retention policy against the current cache size, the cache hit ratio over recent builds, the time the cache saved, and plain-language observations (cache near its size limit, low hit ratio, builds arriving less often than the retention keeps layers).
Use this for "is our cache working", "why are builds not hitting cache", and "are we about to evict layers". It combines depot_get_project (policy), depot_list_project_usage (current size), depot_list_builds (per-build cache counters) and depot_get_usage (minutes billed and saved) so you do not have to.
What it cannot do: Depot's API does not list individual cache entries, so there is no per-layer view, and this server never resets a project's cache. Requires a projectId or DEPOT_PROJECT_ID, and an Organization token.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| projectId | No | The project to summarise. Falls back to DEPOT_PROJECT_ID; depot_list_projects lists the options. | |
| windowDays | No | Usage window in days, ending now, for cache size and minutes saved. Maximum 90. | |
| buildSample | No | How many of the most recent builds to aggregate the hit ratio over. Maximum 100. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| cache | Yes | ||
| notes | Yes | ||
| policy | Yes | ||
| sample | Yes | ||
| window | Yes | ||
| billing | No | ||
| projectId | Yes | ||
| limitations | Yes | ||
| projectName | No | ||
| observations | Yes |