Skip to main content
Glama
peakacom

peaka-mcp-server

Official
by peakacom
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

peaka_create_cache_batch

Create caches for multiple tables in one atomic batch call, preventing partial-failure states when caching many tables. Supports optional ISO-8601 refresh schedules like PT6H or P1D.

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. Dates show when Glama detected each change.

  1. 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"
  2. First observedv0.11.0

TDQS

A4.6/5.0
Behavior4/5

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

The annotations only state readOnlyHint=false and destructiveHint=false. The description adds meaningful behavioral context by revealing that the batch avoids partial-failure states where some caches are created and others aren't. This gives the agent a useful expectation about atomicity. It doesn't mention async behavior or return format, but that is not contradicted by annotations.

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?

Three sentences, each earning its place: the batch purpose, the schedule expression semantics, and the projectId workflow. The main action is front-loaded and there is no filler or repetition of schema content.

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?

The description covers the key selection criteria, schedule behavior, and projectId resolution, which is sufficient for correctly invoking a two-parameter batch creation tool. It could optionally mention checking cache status afterward, but that is not required for making the call 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 description coverage is 100%, so the baseline is 3. The description adds value beyond the schema by giving concrete schedule expression examples (PT6H, P1D, P7D, P30D) and explaining how to discover the projectId when it isn't already known. This operational guidance goes beyond the raw parameter definitions.

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 uses a specific verb and resource: 'Create caches for multiple tables in a single call.' It also differentiates itself from the sibling peaka_create_cache by explicitly mentioning the batch variant, so an agent can identify the tool's scope 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 says explicitly to use this tool 'instead of repeated peaka_create_cache calls when caching many tables' and explains the benefit of avoiding partial failures. It also gives a concrete workflow for resolving an unknown projectId: call peaka_list_projects first and ask the user which project to use.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/peakacom/peaka-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server