Skip to main content
Glama
Sign In
peaka-mcp-server

peaka-mcp-server

Official
by peakacom
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

peaka_create_cache_batch

Create caches for multiple tables in a single call. Use this instead of repeated peaka_create_cache calls when caching many tables.

Instructions

Create caches for multiple tables in a single call. Use this instead of repeated peaka_create_cache calls when caching many tables. Items are processed independently, so some can succeed while others fail: the response contains one entry per item with success, error, and the created cache. Check every entry and report or retry the failed ones rather than assuming the whole batch succeeded. 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

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.8/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the key non-obvious behavior: items are processed independently, partial failure is possible, the response has one entry per item with success/error/created cache, and the agent should check each entry and retry failures. This is exactly the kind of partial-success semantics an agent needs and cannot infer from readOnlyHint=false/destructiveHint=false.

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

Conciseness4/5

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

Front-loads purpose and the sibling routing, then partial-failure guidance. The trailing projectId paragraph is useful but somewhat generic across tools and slightly dilutes the focus; overall still efficient.

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

Completeness5/5

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

No output schema exists, and the description compensates by describing the response shape (one entry per item with success, error, created cache). Combined with the projectId prerequisite and schedule guidance, an agent has everything needed to call this correctly.

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 baseline would be 3; the description adds that each item accepts the same optional schedule expressions as peaka_create_cache, with concrete ISO-8601 examples (PT6H, P1D, P7D, P30D), which helps agents construct nested item objects beyond the schema's own wording.

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?

States a specific verb and resource ('Create caches for multiple tables in a single call') and explicitly contrasts with the singular sibling peaka_create_cache, so an agent can route between them without opening either schema.

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?

Explicitly names the alternative and the condition that selects it ('use this instead of repeated peaka_create_cache calls when caching many tables'), and adds a prerequisite path: if projectId is unknown, call peaka_list_projects and ask the user. Both when-to-use and a dependency ordering are given.

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