Skip to main content
Glama

Restore Carousel Board Version

carousels_board_version_restore
DestructiveIdempotent

Replace a carousel board with a saved version from carousels_board_versions as a new revision; every version stays in the history, so a restore can itself be undone by restoring another. Replaces the latest board unless expectedRevision is set. Identical idempotency keys replay.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "idempotencyKey": "<idempotencyKey>",
      "projectId": "<projectId>",
      "versionId": "<versionId>",
      "expectedRevision": "<expectedRevision>"
    },
    "name": "carousels_board_version_restore"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdYesUUID string.
versionIdYes
workspaceIdNo
idempotencyKeyYes
expectedRevisionYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already cover destructive/idempotent/read-only profile, and the description adds genuinely non-obvious behavior: history is append-only, a restore creates a new revision and is itself undoable, and the target is the latest board unless expectedRevision guards it. It also explains idempotency-key replay semantics that no annotation conveys.

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-loaded with the operation, then the concurrency and idempotency constraints, with no filler. It is a single dense semicolon-chained sentence, which is efficient but slightly harder to scan than split sentences would be.

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?

An output schema exists, so return values need not be described; annotations cover safety. For a destructive restore, the description supplies the missing essentials: target selection, revision guard, and reversibility. Remaining gaps (auth requirements) are minor.

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 only 20%, so the description must compensate, and it does for the two subtle parameters: expectedRevision (a guard on the latest board) and idempotencyKey (identical keys replay). versionId and projectId/workspaceId are left to the schema's type info, but the ambiguity-prone parameters are clarified.

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 (replace a carousel board with a saved version) and names the source collection carousels_board_versions, which also implicitly separates it from the version-listing siblings. An agent can tell this is a restore-from-history operation, not an edit or generate.

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

Usage Guidelines3/5

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

It implies the workflow (restore from carousels_board_versions) and notes the undo path via another restore, but gives no explicit 'use this instead of carousels_board_edit when...' guidance or preconditions. Usage is inferable but not spelled out.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources