peaka_get__data_projects_projectId_cache_cacheId_executionHistory – 1 MCP server offers this tool
What it usually takes
cacheId– in 1 of 1limit– in 1 of 1offset– in 1 of 1projectId– in 1 of 1
No server marks it as only reading: treat it as able to change data.
From each publisher's own tool list. We never call a tool.
Servers
| Server | Inputs | Read-only? |
|---|---|---|
Peaka co.huggingface.ramamatar/peaka Returns a paginated list of past sync executions for the specified cache, ordered from most recent to oldest. Each entry corresponds to one sync run (either incremental or full refresh) and includes its status, progress counters, error details (if failed), and lifecycle timestamps. The `executionMode` field on each entry indicates whether that run was an incremental sync or a full refresh. Use the `limit` and `offset` query parameters to page through history; defaults are `limit=10` and `offset=0`. Execution records have a retention window of 14 days after the cache or run is finalised, after which they are automatically removed. | cacheId,limit,offset,projectId | Not stated |