Skip to main content
Glama
kuklaph
by kuklaph

Manage blocked Cascade tool calls

cascade_tool_blocks
Destructive

Manage guardrails that block Cascade tools from running against specific asset URLs. List current rules or add new blocking rules using tool names and URL selectors.

Instructions

List or add blocked Cascade tool-call rules stored in the local JSON repository.

Use this tool when an agent should persist a guardrail that prevents selected Cascade tools from running against matching asset payloads. Rules require:

  • tools: exact MCP tool names to block, such as cascade_remove or cascade_edit.

  • url: one or more https Cascade CMS asset URLs at /entity/open.act. Each URL must include id and type.

  • type plus id/path for explicit selectors. URL selectors and explicit selectors may be combined.

Actions:

  • list: return the repository path and current rules.

  • add: append rule.

This management tool writes only the local repository. Because add can change guardrails, clients should require user approval before calling this tool. The blocked-call check runs before checked Cascade tools invoke Cascade. 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
actionNoAction to perform against the local tool block repository.
ruleNoRule to append when action is 'add'.
Behavior4/5

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

Annotations indicate destructive and non-read-only behavior. The description adds context: writes only local repository, blocked-call check runs before other tools, and explains response format. No contradiction with annotations.

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 well-structured with clear sections and bullet points. It is slightly verbose but every sentence adds value. Could be trimmed slightly but remains efficient.

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?

Despite lacking an output schema, the description sufficiently explains response behavior (JSON text, structuredContent, cache metadata). It also clarifies the tool's role in the broader toolset, making it complete for an agent.

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% but parameter descriptions are minimal. The description adds significant meaning: action can be 'list' or 'add', and rule requires specific fields (tools, url, type+id/path). This compensates well.

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 manages blocked Cascade tool-call rules with explicit actions (list, add). It distinguishes itself from siblings by focusing on guardrail persistence, which no other sibling tool addresses.

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 gives explicit when-to-use guidance ('persist a guardrail') and details required fields for rules. It also advises user approval for the add action, but does not explicitly state 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