Skip to main content
Glama
kuklaph
by kuklaph

Mark Message

cascade_mark_message
Idempotent

Change a Cascade inbox message's status to read, unread, archive, or unarchive using its identifier.

Instructions

Mark a Cascade inbox message as read, unread, archive, or unarchive.

Toggles the status of a single message. markType controls the action: "read"/"unread" swap the read flag; "archive"/"unarchive" move the message between the inbox and the archive. This is idempotent — marking an already-read message as "read" is a no-op.

Args:

  • identifier (object, required): The message to mark

    • id (string, required): Message ID (from cascade_list_messages)

    • type (string, required): Must be "message"

  • markType (string, required): One of "read" | "unread" | "archive" | "unarchive"

Returns: Cascade OperationResult: { success: true } On failure: { success: false, message: "" }

Examples:

  • Use when: "Mark a workflow notice as read" -> { identifier: { type: "message", id: "..." }, markType: "read" }

  • Use when: "Archive an old notification" -> { identifier: { type: "message", id: "..." }, markType: "archive" }

  • Don't use when: You want to delete — use cascade_delete_message.

  • Don't use when: You want to list — use cascade_list_messages.

Error Handling:

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

  • "Invalid markType" when markType is outside the allowed set

  • "Permission denied" when the message belongs to another user. 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 message to mark.
markTypeNoREQUIRED: Action to apply to the message: 'read' | 'unread' | 'archive' | 'unarchive'.
Behavior4/5

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

Annotations already declare idempotentHint=true, but the description reinforces this by explaining idempotency. Discloses error types like 'Message not found' and 'Permission denied'. However, includes an irrelevant paragraph about cascade_read_response and cascade_read that adds noise and reduces clarity.

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?

Most content is valuable, but the final paragraph about cascade_read_response and cascade_read is irrelevant to this tool and adds unnecessary length. The examples and error handling are well-structured but the extraneous section hurts conciseness.

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?

Covers purpose, parameters, return format (OperationResult), error handling, and usage examples. Lacks an output schema but provides a structured return description. The irrelevant tail about cascade_read_response slightly detracts from completeness.

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

Parameters5/5

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

Schema has 100% description coverage, but the description adds critical context: identifier.id comes from cascade_list_messages, identifier.type must be 'message', and markType allowed values are explicitly listed. This goes beyond the schema's minimal descriptions.

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?

Description clearly states the tool marks a Cascade inbox message as read/unread/archive/unarchive. It distinguishes from siblings like cascade_delete_message and cascade_list_messages by explicitly naming them in the 'Don't use when' section.

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?

Provides explicit when-to-use examples (e.g., 'Mark a workflow notice as read') and when-not-to-use with alternative tool names. Covers both common use cases and exclusions.

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