peaka_get__data_projects_projectId_catalogs_catalogId_schemas_schemaName_tables_tableName_isCached – 1 MCP server offers this tool
What it usually takes
catalogId– in 1 of 1projectId– in 1 of 1schemaName– in 1 of 1tableName– 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 Checks whether the specified table has an active cache in Peaka. When a table is cached, its data is stored locally in Peaka, enabling significantly faster query performance compared to live queries against the original data source. Returns `isCached: true` if a cache is currently active, or `false` otherwise. The response also carries `isCacheable` and `supportedCacheTypes` (`FULL_REFRESH`, `INCREMENTAL`), so a single call is enough to decide whether — and with which schedule types — a cache can be created for the table. `supportedCacheTypes` is empty when the table is not cacheable; both fields are absent when the information could not be resolved. | catalogId,projectId,schemaName,tableName | Not stated |