Skip to main content
Glama

Change the owner's notifications

dosai_update_notification_settings
Destructive

Set about what the platform notifies the OWNER and his WhatsApp number for it (never a client's address; sent from the project's own connected WhatsApp). Events: lead_created (a new lead or deal appeared), lead_status_changed (the bot moved a deal to another stage), payment_received (a client paid), crm_digest (the CRM "Today" digest every morning at 9:00). events replaces the whole list. Email: dosai_set_notify_email. Telegram: dosai_connect_owner_telegram. Daily report: dosai_set_daily_report. Check: dosai_send_test_notification. Requires admin or owner role.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project_id": "<project_id>"
    },
    "name": "dosai_update_notification_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
eventsNo
project_idYesFrom dosai_list_projects.
whatsapp_phoneNoOwner's WhatsApp number like +77011234567; empty string switches it off.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / events / items / enum
      Previous value: -[
      -  "conversation_started",
      -  "lead_created",
      -  "lead_status_changed",
      -  "payment_received",
      -  "crm_digest"
      -]New value: +[
      +  "lead_created",
      +  "lead_status_changed",
      +  "payment_received",
      +  "crm_digest"
      +]
    • changedInput schema / properties / events / maxItems
      Previous value: -5New value: +4
  2. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / project_id / description
      Previous value: -"Project id, as returned by dosai_list_projects."New value: +"From dosai_list_projects."
  3. Changed1 schema field changed
    • removedInput schema / properties / project_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  4. Added

TDQS

A4/5.0
Behavior4/5

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

Goes well beyond the annotations (destructiveHint=true, readOnlyHint=false) by disclosing the key destructive semantic: '`events` replaces the whole list.' It also constrains scope (owner's number only, never a client's; messages sent from the project's own connected WhatsApp) and states the role requirement. It does not explain what happens if events is omitted, which is the one behavioral ambiguity left for a mutation tool.

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?

Front-loads the purpose and event list, then compresses cross-references into terse 'Channel: tool_name' fragments. Dense but mostly waste-free; the awkward opening clause and fragmented syntax cost a little readability without adding noise.

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?

For a 3-parameter mutation tool with no output schema and no annotations covering semantics, the description supplies the destructive replace behavior, channel routing, event meanings and auth requirement. The only material gap is the effect of omitting `events` or `whatsapp_phone` (partial-update semantics).

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 67% and the description adds real meaning on top: it defines each enum value in business terms (lead_created = new lead or deal appeared, lead_status_changed = bot moved a deal, crm_digest = 9:00 daily digest) where the schema lists bare strings, and clarifies whose WhatsApp number the parameter refers to. It does not restate the empty-string off-switch or phone format, which the schema already covers.

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?

Names a specific verb+resource (setting what the platform notifies the OWNER) and enumerates the four events with plain-language glosses, so the agent knows exactly what is controlled. The opening clause 'Set about what the platform notifies' is grammatically garbled, which slightly blunts an otherwise precise statement.

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?

Explicitly routes adjacent concerns to siblings: email via dosai_set_notify_email, Telegram via dosai_connect_owner_telegram, daily report via dosai_set_daily_report, and verification via dosai_send_test_notification. It also states the prerequisite ('Requires admin or owner role'), though it never explicitly says when to prefer this over dosai_get_notification_settings (read vs write is implied by the verb only).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources