Skip to main content
Glama
peakacom

peaka-mcp-server

Official
by peakacom
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

peaka_create_cache_batch

Create caches for multiple tables in one atomic batch call, preventing partial failures. Supports optional schedule expressions for each table.

Instructions

Create caches for multiple tables in a single call. Use this instead of repeated peaka_create_cache calls when caching many tables — it avoids partial-failure states where some caches are created and others aren't. Each item supports the same optional schedule expressions as peaka_create_cache (ISO-8601 durations, e.g. PT6H, P1D, P7D, P30D).

If you do not already know the projectId for the current task, call peaka_list_projects first and ask the user which project to use. Remember the chosen projectId for subsequent calls in this conversation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYesTables to cache. Must contain at least one item.
projectIdYesThe Peaka project ID to run against.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.15.1
    • removedInput schema / properties / items / items / properties / fullRefreshSchedule / $ref
      Removed value: -"#/properties/items/items/properties/incrementalSchedule"
    • addedInput schema / properties / items / items / properties / fullRefreshSchedule / anyOf
      Added value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "expression": {
+        "description": "ISO-8601 duration between refreshes, e.g. PT6H, P1D, P7D, P30D.",
+        "pattern": "^P(?!$)(\\d+Y)?(\\d+M)?(\\d+W)?(\\d+D)?(T(?=\\d)(\\d+H)?(\\d+M)?(\\d+S)?)?$",
+        "type": "string"
+      },
+      "type": {
+        "const": "BASIC",
+        "type": "string"
+      }
+    },
+    "required": [
+      "type",
+      "expression"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "type": {
+        "const": "NONE",
+        "type": "string"
+      }
+    },
+    "required": [
+      "type"
+    ],
+    "type": "object"
+  }
+]
  2. Changed6 schema fields changedv0.12.2
    • addedInput schema / properties / items / items / properties / fullRefreshSchedule / $ref
      Added value: +"#/properties/items/items/properties/incrementalSchedule"
    • changedInput schema / properties / items / items / properties / fullRefreshSchedule / description
      Previous value: -"Optional ISO-8601 duration for the full refresh schedule, e.g. P7D, P30D."New value: +"Optional full refresh schedule. {type: 'BASIC', expression: 'P7D'} for recurring, or {type: 'NONE'} to leave it off."
    • removedInput schema / properties / items / items / properties / fullRefreshSchedule / type
      Removed value: -"string"
    • addedInput schema / properties / items / items / properties / incrementalSchedule / anyOf
      Added value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "expression": {
+        "description": "ISO-8601 duration between refreshes, e.g. PT6H, P1D, P7D, P30D.",
+        "pattern": "^P(?!$)(\\d+Y)?(\\d+M)?(\\d+W)?(\\d+D)?(T(?=\\d)(\\d+H)?(\\d+M)?(\\d+S)?)?$",
+        "type": "string"
+      },
+      "type": {
+        "const": "BASIC",
+        "type": "string"
+      }
+    },
+    "required": [
+      "type",
+      "expression"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "type": {
+        "const": "NONE",
+        "type": "string"
+      }
+    },
+    "required": [
+      "type"
+    ],
+    "type": "object"
+  }
+]
    • changedInput schema / properties / items / items / properties / incrementalSchedule / description
      Previous value: -"Optional ISO-8601 duration for the incremental refresh schedule, e.g. PT6H, P1D."New value: +"Optional incremental refresh schedule. {type: 'BASIC', expression: 'PT6H'} for recurring, or {type: 'NONE'} to leave it off."
    • removedInput schema / properties / items / items / properties / incrementalSchedule / type
      Removed value: -"string"
  3. First observedv0.11.0

TDQS

A4.6/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only indicate the tool is not read-only and not destructive, so the description adds meaningful behavior: batch creation avoids partial-failure states where some caches are created and others are not. It also notes that schedule expressions mirror peaka_create_cache, helping the agent understand expected input behavior without opening the sibling tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core purpose, immediately followed by the key differentiator and schedule support. The projectId guidance is placed at the end but earns its place. There is no redundant restatement of schema details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a batch-creation tool with two required parameters and no output schema, the description adequately covers the primary workflow: when to use it, what schedule formats are accepted, and how to resolve projectId. It does not describe the return value, but the schema and annotations already carry most of the call-level requirements.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents all parameters and their formats. The description adds value by giving concrete ISO-8601 examples (PT6H, P1D, P7D, P30D), clarifying that schedules are optional, and explaining how to obtain projectId through peaka_list_projects.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: 'Create caches for multiple tables in a single call.' It explicitly distinguishes itself from peaka_create_cache by framing itself as the batch alternative for many tables, so an agent can tell them apart immediately.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit when-to-use rule: use this instead of repeated peaka_create_cache calls when caching many tables, to avoid partial-failure states. It also tells the agent to call peaka_list_projects first if projectId is unknown and to remember the chosen projectId, which is concrete navigational guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools