Skip to main content
Glama
kuklaph
by kuklaph

Read System Preferences

cascade_read_preferences
Read-onlyIdempotent

Reads all Cascade CMS system preferences including publish, image, API, and UI settings. Use this to review current values before editing them.

Instructions

Read all Cascade system preferences.

Returns every configurable server-wide preference as name/value pairs. Preferences include things like default publish behavior, image handling defaults, API limits, and UI options. Typically useful before calling cascade_edit_preference so you know the current value. Requires system-admin-level credentials.

Args: (none)

Returns: Cascade OperationResult: { success: true, preferences: [ { name: "...", value: "..." }, ... ] } On failure: { success: false, message: "" }

Examples:

  • Use when: "What's the current publish-on-save setting?" -> {}

  • Use when: "Inspect all server preferences" -> {}

  • Don't use when: You want user-level settings — preferences are system-wide.

  • Don't use when: You only need one preference — still call this (there's no read-single endpoint), then filter client-side.

Error Handling:

  • "Permission denied" when credentials lack system-admin rights

  • "Authentication failed" when the API key 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

No arguments

Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, but description adds credential requirements, error handling details, and the return format. No contradiction. The extra paragraph on structured content seems irrelevant but does not mislead.

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?

Front-loaded with purpose and return format, but includes a somewhat irrelevant boilerplate paragraph about read_mode and structured content that appears copied from another tool. This adds unnecessary length.

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?

Despite the extraneous boilerplate, the description covers behavior, error handling, usage examples, and differentiation from sibling tools. No output schema exists, but the return format is described. Mostly complete for a zero-parameter tool.

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?

No parameters exist, and the description explicitly states 'Args: (none)' with example usage showing empty input. Schema coverage is 100%, so no additional parameter info needed. Baseline 4 applies.

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 'Read all Cascade system preferences' and elaborates with examples of preference types. It distinguishes from siblings like cascade_edit_preference by advising to check current values before editing, and from user-level tools by noting preferences are system-wide.

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?

Explicitly stated when to use (to inspect or check before editing) and when not to use (for user-level settings). It also requires system-admin-level credentials, providing clear prerequisites.

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