Skip to main content
Glama
Cloady

Cloady

Official
by Cloady

Update Notification Preferences

updateNotificationPreferences
Destructive

Adjust your Cloady notification settings for billing, deployments, incidents, tickets, replies, product updates, and weekly summaries.

Instructions

Update notification preferences for the current user

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": "updateNotificationPreferences"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestBodyNoThe JSON request body.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.18.0
    • addedInput schema / properties / requestBody / properties / deploys / description
      Added value: +"Deploy result emails: off, failures only, failures plus the deploy that fixes one, or every deploy. An app's first live deploy is always emailed"
    • addedInput schema / properties / requestBody / properties / deploys / enum
      Added value: +[
      +  "off",
      +  "failures",
      +  "fixes",
      +  "all"
      +]
    • changedInput schema / properties / requestBody / properties / deploys / type
      Previous value: -"boolean"New value: +"string"
    • addedInput schema / properties / requestBody / properties / replies
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / requestBody / properties / tickets
      Added value: +{
      +  "type": "boolean"
      +}
  2. First observedv0.5.1

TDQS

C2.9/5.0
Behavior2/5

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

The annotations declare destructiveHint=true and openWorldHint=true, but the description adds nothing about what that destruction means — whether omitted fields are reset to defaults or preserved, whether the whole preference set is replaced, or whether the change is reversible. With a destructive mutation and no output schema, the only added value is the "current user" scoping, which is thin.

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?

A single front-loaded sentence with zero filler; it is efficiently sized. However, that efficiency is partly under-specification rather than disciplined editing, so it does not reach 5.

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

Completeness2/5

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

For a destructive, open-world mutation with a nested request body and no output schema, the description is far too sparse. An agent still cannot determine whether this is a partial patch or a full replace, what happens to unset fields, or what confirmation the response gives.

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

Parameters3/5

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

Schema coverage is reported at 100% for the single requestBody parameter, so the baseline is 3, but the description contributes nothing about the body. The nested object holds seven fields (weekly, billing, deploys, product, replies, tickets, incidents), most of which are undocumented booleans whose default/omitted semantics matter for a destructive update.

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?

States a specific verb and resource ("Update notification preferences") scoped to "the current user", which is unambiguous. It does not mention the obvious counterpart sibling getNotificationPreferences or otherwise differentiate itself from the many other update* tools, so it stays at 4 rather than 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no prerequisites, and no pointer to getNotificationPreferences for reading current values first. The agent must infer usage purely from the name; nothing states whether this call is additive or a full replacement.

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

Deploy Server

Other Tools