Skip to main content
Glama
kuklaph
by kuklaph

List cached raw asset facts

cascade_asset_list_facts
Read-onlyIdempotent

Lists indexed facts from a cached Cascade response, supporting pointer, key, value, scalar, and reference filters with cursor pagination. Returns JSON with fact details or bounded cache metadata for large responses.

Instructions

Use after cascade_read. List object, array, key, and scalar facts indexed from the full cached raw Cascade response. Supports pointer, key, value, scalar, and reference filters with cursor pagination. This tool never reads Cascade directly and reports complete: true only when the current filter has no remaining matches. 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
asset_handleNoREQUIRED: Asset handle returned by cascade_read structuredContent.asset_handle.
pointer_prefixNo
fact_kindNo
keyNo
key_containsNo
value_containsNo
scalar_typeNo
non_emptyNo
reference_kindNo
cursorNo
limitNo
Behavior5/5

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

Beyond annotations (readOnlyHint, idempotentHint), the description adds critical behavioral details: never reads Cascade directly, complete flag behavior, response format (JSON text vs structuredContent), overflow handling with _cache metadata, and relationship to cascade_read read_mode.

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 concise yet comprehensive, with every sentence adding value. It front-loads the primary purpose and efficiently packs behavioral, usage, and response details.

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 the tool's complexity (11 parameters, no output schema), the description covers key aspects: data source, filtering capabilities, pagination, response format, and integration with cascade_read. It lacks detailed parameter descriptions but is otherwise complete for a list tool.

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?

With only 9% schema description coverage (only asset_handle described), the description mentions filter types (pointer, key, value, scalar, reference) and cursor pagination, but does not explain each of the 11 parameters individually, leaving significant ambiguity.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool lists cached raw asset facts, with specific mention of object, array, key, and scalar facts, filters, and pagination. It avoids tautology but does not explicitly differentiate from sibling tools like cascade_asset_list_nodelets.

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?

The description advises 'Use after cascade_read' and explains the tool never reads Cascade directly, providing context for when to use. However, it does not exclude alternatives or specify when not to use this tool.

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