`peaka_post__data_projects_projectId_catalogs_catalogId_parametricTables` – 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` Creates a new Parametric Table under the specified catalog. A Parametric Table binds specific query parameter values to a source table from a REST catalog, producing a new named table (e.g., `xyz_customers`) that can be queried directly without supplying those parameters at query time. For example, if the source table `customers` requires a `_q_account` parameter, you can create a Parametric Table that fixes this value and exposes the result as a standalone table. Date and timestamp parameters also accept relative-date macros, re-evaluated on every query, so a table saved as "this week's sales" always returns the current week. Grammar: `@<anchor>[(+\|-)<n><unit>]` - Anchors: `@today`, `@yesterday`, `@now` (current instant), `@sow` / `@eow` (week, Monday start), `@som` / `@eom` (month), `@soq` / `@eoq` (quarter), `@soy` / `@eoy` (year) - Units: `d` day, `w` week, `M` month, `q` quarter, `y` year, `h` hour, `m` minute (lowercase `m` is minute, uppercase `M` is month) - Offsets can be	`catalogId`,`projectId`,`request_body`	Not stated