Skip to main content
Glama

update_client_notification_settings

Change a client's reminder settings on their behalf (e.g. quiet hours for a night-shift client). Only the fields given change. (confirm-gated: previews until confirm: true)

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": {
      "clientId": "<clientId>",
      "input": "<input>"
    },
    "name": "update_client_notification_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes
confirmNoMust be true to actually execute. If false/omitted, returns a preview only.
clientIdYesClient's User _id (from list_clients)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, and the description adds genuinely new behavior: partial-update semantics ('Only the fields given change') and the confirm-gated preview flow. That tells the agent a call without confirm: true is safe and non-mutating, which the annotations alone do not convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact sentences plus a parenthetical: purpose first, then the partial-update rule, then the confirm gate. No filler and every clause carries information an agent needs before calling.

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 small mutation tool with a nested input object and no output schema, the description covers purpose, partial-update semantics, and the confirm gating that governs execution. It could say more about what a preview returns, but nothing critical for correct invocation is missing.

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 67% and both confirm and clientId are already well documented in the schema, including the preview/execute contract. The description's only real addition is the partial-update rule for the input object and the quiet-hours example; it does not explain emailReminders/pushReminders or the timezone interaction beyond what the schema states.

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 ('Change a client's reminder settings') and adds scope via 'on their behalf', which implicitly separates it from update_my_notification_settings. It does not name the sibling outright, but the client-vs-self distinction is unambiguous.

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

Usage Guidelines3/5

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

The 'on their behalf' phrasing and the night-shift quiet-hours example imply the coach-administering-for-a-client scenario, but no explicit when-not guidance or named alternative (e.g. update_my_notification_settings for self) is given. Usage is inferable rather than stated.

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.