Skip to main content
Glama
kuklaph
by kuklaph

Read Cascade Asset

cascade_read
Read-onlyIdempotent

Read an asset from Cascade CMS by identifier. Preview mode returns compact asset handle and node outline; raw mode returns the full REST payload.

Instructions

Read an asset from Cascade CMS by identifier.

Default preview mode returns a compact browse-oriented asset_handle, asset identity, raw_hash, index_version, fact/reference counts, node counts, root nodelet outline, and raw_resource_uri. Preview is not audit-complete; use cascade_asset_list_facts, cascade_asset_search_values, cascade_asset_search_keys, cascade_asset_get_value, cascade_asset_list_scalar_artifacts, cascade_asset_list_references, cascade_asset_list_nodelets, and cascade_asset_get_nodelet with the returned asset_handle for follow-up inspection. Use read_mode: "raw" only when the full REST payload is required.

Args:

  • identifier (object, required): The asset to read

    • id (string, optional): Cascade internal asset ID (e.g., "d3631e59ac1e..."). Takes priority over path when both are provided.

    • path (object, optional): Site-qualified path

      • path (string, required): Asset path within the site, starting from root (e.g., "/about/team")

      • siteId OR siteName (string): Which site the path belongs to

    • type (string, required): Entity type — one of the 56 EntityTypeString values (page, file, folder, block, template, etc.)

    • recycled (boolean, optional): Read from recycle bin.

  • read_mode (string, optional): 'preview' (default, compact handle-based output) or 'raw' (full REST payload; expensive for structured assets). Returns: Preview mode: { asset_handle, asset_type, asset_identity, raw_resource_uri, raw_hash, index_version, audit_complete: false, total_fact_count, reference_count, node_count, max_depth, root_outline, omitted_fields, warnings, next_actions } Raw mode: { success: true, asset: { : { ...type-specific representation } } } On failure: { success: false, message: "Asset not found" }

Examples:

  • Use when: "Read the homepage" -> { identifier: { type: "page", path: { path: "/", siteName: "www" } } }

  • Use when: "Get file by ID" -> { identifier: { type: "file", id: "abc123..." } }

  • Use when: "Load folder config" -> { identifier: { type: "folder", path: { path: "/about", siteName: "www" } } }

  • Don't use when: You want to modify — use cascade_edit instead.

  • Don't use when: You want to check access rights — use cascade_read_access_rights.

Error Handling:

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

  • "Permission denied" when credentials lack read access

  • "Site not found" when siteName/siteId is invalid. 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 read. Provide id + type (preferred) or path + type.
read_modeNoRead mode for cascade_read. 'preview' (default) returns a compact asset_handle plus nodelet outline for structured assets. 'raw' returns the full Cascade REST payload and can be expensive for pages or data-definition blocks.
Behavior5/5

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

Discloses that preview mode is not audit-complete, raw mode is expensive, and lists possible error responses. Annotations already indicate read-only and idempotent, and the description adds context about behavior and limitations.

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?

Well-organized into sections with clear headings. While lengthy, every section adds necessary detail. Slightly verbose but still concise for the complexity.

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?

Given no output schema, the description fully specifies return shapes for both modes and error handling. All necessary context for correct invocation is provided.

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% with descriptions; the description adds examples, clarifies id priority over path, and explains read_mode options, providing additional value 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 it reads an asset from Cascade CMS by identifier. It distinguishes preview vs raw mode and references sibling tools for follow-up inspection, making the purpose unambiguous.

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 'Use when' and 'Don't use when' examples guide the agent, including naming alternative tools like cascade_edit for modifications and cascade_read_access_rights for access checks.

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