Skip to main content
Glama

update_my_notification_settings

Change the coach's own reminder settings. 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": {
      "input": "<input>"
    },
    "name": "update_my_notification_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes
confirmNoMust be true to actually execute. If false/omitted, returns a preview only.

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 declare this is a non-destructive, non-open-world write, and the description adds two traits beyond them: patch-style semantics ('Only the fields given change') and the confirm-gated preview-then-execute flow. That is meaningful behavioral context, though it does not say what a preview contains or when changes take effect.

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 tight sentences: the mutation target and scope come first, then the partial-update rule, then the gating constraint in a short parenthetical. No sentence is wasted and nothing is buried.

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 two-parameter update with a nested quietHours object and no output schema, the description covers scope, merge behavior, and the safety gate, which is enough to invoke correctly. The main remaining gap is what the preview response looks like, though it is minor.

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?

With 50% schema description coverage, the description compensates partially: 'Only the fields given change' clarifies that the optional boolean/quietHours fields are partial, and the parenthetical clarifies the confirm flag's effect. The quietHours shape and timezone semantics come from the schema, not the description, so it adds only modest value.

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?

The description names a specific verb and resource ('Change the coach's own reminder settings') and the possessive 'own' signals the scope is the caller, which distinguishes it from the sibling update_client_notification_settings without naming it. It stops short of explicit sibling routing, so it is clear but not fully differentiated.

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 confirm-gate sentence effectively tells the agent that a false/omitted confirm yields a preview, which is practical invocation guidance. However, there is no explicit statement of when to use this versus update_client_notification_settings or when to call get_my_notification_settings first, so usage is only implied.

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.