Skip to main content
Glama
kuklaph
by kuklaph

Check Out Asset

cascade_check_out

Lock a Cascade asset for exclusive editing by creating a working copy that only you can edit. Required before modifying files or binary content.

Instructions

Lock a Cascade asset for exclusive editing.

Check-out creates a working copy of the asset that only the authenticated user can edit; other users see the previously committed version until check-in. Required for some asset types (especially files and binary content types) before cascade_edit will succeed. The response includes a workingCopyIdentifier that represents the locked working copy for subsequent calls. Always pair with cascade_check_in when editing finishes to release the lock.

Args:

  • identifier (object, required): The asset to check out

    • id (string, optional): Asset ID (preferred)

    • path (object, optional): { path, siteId OR siteName }

    • type (string, required): Entity type of the asset

Returns: Cascade OperationResult: { success: true, workingCopyIdentifier?: { id, type, path: { path, siteId, siteName } } } On failure: { success: false, message: "" }

Examples:

  • Use when: "Lock a page before editing" -> { identifier: { type: "page", id: "..." } }

  • Use when: "Check out a file for binary replacement" -> { identifier: { type: "file", path: { path: "/assets/logo.png", siteName: "www" } } }

  • Don't use when: You've finished editing — use cascade_check_in to release.

  • Don't use when: Read-only operations — checkout isn't needed for cascade_read.

Error Handling:

  • "Asset not found" when the identifier doesn't resolve

  • "Already checked out" when another user holds the lock

  • "Permission denied" when credentials lack edit rights. Responses are JSON text; structuredContent is authoritative when the response fits. Oversized responses return bounded _cache metadata for cascade_read_response. For cascade_read, read_mode controls preview versus raw Cascade payload shape.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
identifierNoThe asset to check out (creates a working copy for exclusive editing).
Behavior4/5

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

Discloses behavioral traits: required for some asset types, creates working copy, only user can edit, others see previous version, response includes workingCopyIdentifier, must pair with check_in. Annotations already indicate non-readonly and non-destructive. The description adds context beyond annotations. Minor deduction for irrelevant tail about structuredContent.

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

Conciseness3/5

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

Description is long but well-structured with sections. However, it includes irrelevant text about structuredContent and cascade_read that doesn't belong, reducing conciseness.

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?

Given no output schema, the description provides a clear return schema and error handling. Examples and pairing with sibling are provided. Slightly incomplete due to irrelevant tail, but overall adequate for the tool's complexity.

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 is minimal ('The asset to check out...'). The description's Args section adds nested structure (id, path, type) with constraints (type required, id preferred). This adds significant meaning beyond 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 clearly states that the tool locks a Cascade asset for exclusive editing, creating a working copy. It distinguishes from sibling tools like cascade_check_in for releasing the lock.

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?

Explicit when-to-use guidance (before editing, for certain asset types) and when-not-to (finished editing, read-only operations). Also references cascade_check_in as the counterpart.

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/kuklaph/cascade-cms-mcp-server'

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