`peaka_get__data_projects_projectId_cache_cacheId_status` – 1 MCP server offers this tool

What it usually takes

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.

Server	Inputs	Read-only?
Peaka `co.huggingface.ramamatar/peaka` Returns the current status of a specific cache, including execution details for both the last incremental sync and the last full refresh. The top-level `status` field is computed from the most recent execution across both sync types: - `NOT_INITIALIZED`: No sync has ever been executed for this cache. - `RUNNING`: At least one sync (incremental or full refresh) is currently in progress. - `COMPLETED`: The most recent sync completed successfully. - `FAILED`: The most recent sync failed. Check the `error` field in the relevant execution info for details. - `CANCELLED`: The most recent sync was cancelled via a cancel endpoint. Each execution info object (`lastIncrementalCacheExecution`, `lastFullRefreshCacheExecution`) contains: - `id`: Unique execution identifier. - `status`: Execution-specific status (RUNNING, COMPLETED, FAILED, CANCELLED). - `progress`: Real-time progress with record counts (cached, inserted, updated, deleted). - `error`: Error details if the execution failed. - `create	`cacheId`,`excludeLogs`,`projectId`	Not stated