Skip to main content
Glama

Coline

Update Messages settings

update_messages_settings
Idempotent

Changes the person's do not disturb, quiet or working hours, status, away time or digests. Only the fields you pass change.

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": {
      "workspace": "<workspace>"
    },
    "name": "update_messages_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
dndUntilNoDo not disturb until then; null turns it off.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
quietHoursNo
customStatusNo
workingHoursNo
deviceSchedulesNo
digestFrequencyNo
digestTimeMinutesNo
smartInterruptionsNo
automaticAwayMinutesNo
missedActivityEmailsNo
customStatusExpiresAtNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare this is non-destructive, idempotent, and not read-only, so the safety profile is covered. The description adds meaningful behavioral context with "Only the fields you pass change," clarifying partial-update semantics. However, it does not explain the scope of "the person" (self vs. others) or the effect of null values across the various setting objects.

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 short sentences with no filler. The field categories are front-loaded and the partial-update rule follows immediately, so every sentence earns its place.

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

Completeness3/5

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

An output schema exists, so return values need not be explained. The definition covers the core purpose and partial-update behavior for a 12-parameter mutation, but the large number of undocumented parameters leaves meaningful gaps in completeness.

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

Parameters2/5

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

Schema description coverage is only 17%, so the description must carry most parameter meaning, and it only partially does so. It names broad categories such as do not disturb, quiet/working hours, status, away time, and digests, but leaves many of the 12 parameters, including device schedules, smart interruptions, missed activity emails, and digest timing, without any descriptive explanation.

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 gives a specific verb ("Changes") and enumerates the resource areas being modified: do not disturb, quiet/working hours, status, away time, and digests. It is clear enough for an agent to identify the operation, but it does not explicitly distinguish this from the sibling get_messages_settings tool.

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?

The description implies usage by virtue of being an update tool, but provides no explicit when-to-use guidance, no alternatives, and no prerequisites beyond the schema's required workspace parameter. An agent must infer that get_messages_settings is the read counterpart rather than being told.

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