peaka_put__data_projects_projectId_cache_cacheId – 1 MCP server offers this tool
What it usually takes
cacheId– in 1 of 1projectId– in 1 of 1request_body– 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 Updates the sync schedules of an existing cache. Use this to change how frequently the cache is refreshed. Only schedule fields are updated; the target table, catalog, and schema cannot be changed after creation. When a schedule is changed, any previously running scheduled workflow for that mode is replaced with the new schedule. Set a schedule's `type` to `NONE` to disable that particular sync mode. The schedule `expression` uses ISO-8601 duration format (e.g. `PT6H` = every 6 hours, `PT15M` = every 15 minutes, `P1D` = every day). | cacheId,projectId,request_body | Not stated |