Skip to main content
Glama
peakacom

peaka-mcp-server

Official
by peakacom
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

peaka_update_cache

Idempotent

Update cache refresh settings by replacing both incremental and full refresh schedules with ISO-8601 durations or NONE to disable.

Instructions

Update cache settings on an existing cache in the Peaka project. This endpoint replaces — not merges — the schedules, so both incrementalSchedule and fullRefreshSchedule must be supplied with the full intended state every call. Each schedule is either {type: "BASIC", expression} with an ISO-8601 duration (e.g. PT6H, P1D, P7D, P30D), or {type: "NONE"} to turn that refresh off. The response reflects the schedule actually applied, which the backend may clamp to its allowed range — check it.

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
cacheIdYesThe cache ID to update. Available from peaka_get_cache_statuses.
projectIdYesThe Peaka project ID to run against.
fullRefreshScheduleYesFull refresh schedule. Required — replaces the existing value. {type: 'BASIC', expression: 'P7D'} for recurring, or {type: 'NONE'} to disable.
incrementalScheduleYesIncremental refresh schedule. Required — replaces the existing value. {type: 'BASIC', expression: 'PT6H'} for recurring, or {type: 'NONE'} to disable.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.15.1
    • changedInput schema / properties / fullRefreshSchedule / anyOf
      Previous value: -[
-  {
-    "$ref": "#/properties/incrementalSchedule/anyOf/0"
-  },
-  {
-    "$ref": "#/properties/incrementalSchedule/anyOf/1"
-  }
-]New 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 / fullRefreshSchedule / anyOf
      Added value: +[
+  {
+    "$ref": "#/properties/incrementalSchedule/anyOf/0"
+  },
+  {
+    "$ref": "#/properties/incrementalSchedule/anyOf/1"
+  }
+]
    • changedInput schema / properties / fullRefreshSchedule / description
      Previous value: -"ISO-8601 duration for the full refresh schedule, e.g. P7D, P30D. Required — replaces the existing value."New value: +"Full refresh schedule. Required — replaces the existing value. {type: 'BASIC', expression: 'P7D'} for recurring, or {type: 'NONE'} to disable."
    • removedInput schema / properties / fullRefreshSchedule / type
      Removed value: -"string"
    • addedInput schema / 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 / incrementalSchedule / description
      Previous value: -"ISO-8601 duration for the incremental refresh schedule, e.g. PT6H, P1D. Required — replaces the existing value."New value: +"Incremental refresh schedule. Required — replaces the existing value. {type: 'BASIC', expression: 'PT6H'} for recurring, or {type: 'NONE'} to disable."
    • removedInput schema / properties / incrementalSchedule / type
      Removed value: -"string"
  3. First observedv0.11.0

TDQS

A4.7/5.0
Behavior5/5

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

The description adds valuable non-obvious behavior beyond annotations: replace-not-merge semantics, the need to send the full intended state every call, and the warning that the backend may clamp the applied schedule and that the response reflects that. These are exactly the behavioral details an agent needs to avoid incorrect calls.

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 and replace semantics, then gives compact examples and a practical prerequisite. Every sentence carries useful information, with no padding or repetition.

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?

For a four-required-parameter update tool with no output schema, the description covers the schedule format, the replace behavior, the clamping caveat, and the projectId discovery flow. Nothing essential is missing for an agent to invoke it 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 the baseline is 3, but the description adds meaningful plain-language semantics: explaining the BASIC/NONE shape, giving ISO-8601 examples, and emphasizing that the schedules are replaced wholesale. This elevates it above merely restating the schema.

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 ('Update cache settings'), a specific resource ('an existing cache in the Peaka project'), and prominently distinguishes the behavior from merging by saying the endpoint 'replaces — not merges'. This clearly sets it apart from create/refresh/delete siblings.

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

Usage Guidelines4/5

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

It gives clear operational guidance: both schedules must be supplied in full, and if projectId is unknown, call peaka_list_projects first and ask the user. It does not explicitly name alternatives, but the context of updating an existing cache and the prerequisite flow make usage sufficiently clear.

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