cascade-cms-mcp-server

List cached raw scalar artifacts

cascade_asset_list_scalar_artifacts

Read-onlyIdempotent

Lists derived link/path artifacts (http_url, site_link, href, src, etc.) from cached raw string facts, returning JSON pointer and offset provenance. Use after cascade_read.

Instructions

Use after cascade_read. Enumerate derived link/path-like artifacts from cached raw string scalar facts, including http_url, site_link, href, src, anchor, mailto, tel, and root_path. Returns JSON Pointer and offset provenance. This tool never reads Cascade directly. 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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "cascade_asset_list_scalar_artifacts"
  }
}

Input Schema

Name	Required	Description
`asset_handle`	No	REQUIRED: Asset handle returned by cascade_read structuredContent.asset_handle.
`artifact_kind`	No
`pointer_prefix`	No
`key`	No
`key_contains`	No
`value_contains`	No
`cursor`	No
`limit`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.2May 26, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive behavior. The description adds valuable details beyond annotations: 'never reads Cascade directly,' explains response format (JSON text with structuredContent authority and _cache metadata for oversized responses). This enhances transparency.

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?

The description is relatively concise and front-loaded with the core purpose. It uses multiple sentences but each adds meaningful information. However, it could be more structured by separating usage guidelines from behavioral notes.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 8 parameters with low schema coverage and no output schema, the description provides some behavioral context (response handling, cursor? not mentioned) but lacks details on return structure beyond 'JSON Pointer and offset provenance.' Pagination and parameter usage are not explained, making it incomplete for complex scenarios.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 13% (only asset_handle described). The description does not explain other parameters like artifact_kind, pointer_prefix, cursor, limit, etc. It lists artifact types but doesn't map them to parameters, leaving the agent without sufficient guidance on how to filter or paginate.

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 the tool enumerates derived link/path-like artifacts from cached raw string scalar facts, listing specific types like http_url, site_link, href, etc. It distinguishes from siblings like cascade_asset_list_facts by focusing on scalar artifacts rather than general facts.

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?

The description explicitly says 'Use after cascade_read,' providing clear context for when to invoke the tool. It does not explicitly mention alternatives or when not to use it, but the instruction is sufficient given the sibling context.

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

Deploy Server