`peaka_post__data_projects_projectId_cache_cacheId_fullRefreshUpdate` – 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` Manually triggers a full refresh (resync) for the specified cache. This drops all existing cached data and rebuilds the cache from scratch by re-reading the entire source table. Full refresh is more expensive than incremental sync but ensures complete data consistency. It is useful when the source data has drifted or when schema changes have occurred. This is a one-time manual trigger that runs independently of any configured schedule. Use the Get Cache Status endpoint to monitor the progress of the triggered refresh. The `lastFullRefreshCacheExecution` field in the status response will reflect the new execution.	`cacheId`,`projectId`	Not stated