Skip to main content
Glama

Coline

Set conversation notifications

set_conversation_notifications
Idempotent

Sets how the person hears about a conversation: everything, mentions only or nothing; or mutes or snoozes it until a time.

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>",
      "type": "<type>",
      "conversationId": "<conversationId>"
    },
    "name": "set_conversation_notifications"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYes
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
mutedUntilNo
snoozedUntilNo
conversationIdYesChannel or direct message id, from list_conversations.
notificationLevelNo

Output Schema

NameRequiredDescriptionDefault
notificationLevelYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so safety is covered and the description only needs to add semantics. It does disclose the outcome of the operation (delivery level, muting, snoozing until a time), but leaves a real behavioral ambiguity: whether 'mute' and 'snooze' are distinct modes, and whether setting a notificationLevel clears an existing mute/snooze or coexists with it.

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?

A single sentence that front-loads the core effect and then packs the enum values and the time-based variants into one clause, with no filler. Nothing could be removed without losing meaning.

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, and the annotations cover safety. However, for a 6-parameter mutation with only 33% schema coverage, the definition omits the mute-vs-snooze distinction and the mutual exclusivity of the level and time parameters, leaving an agent guessing at how to fill three undocumented fields.

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 only 33% — only workspace and conversationId carry descriptions — so the description has to compensate. It usefully maps 'everything, mentions only or nothing' onto the notificationLevel enum and hints at mutedUntil/snoozedUntil, but it never explains the difference between those two nearly identical date-time parameters, nor what type='channel' vs 'dm' changes, which is exactly the gap the schema leaves open.

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 ('Sets') and a specific resource ('how the person hears about a conversation'), then enumerates the possible states (everything, mentions only, nothing, mute, snooze). That is far more precise than the bare name, but it never positions itself against notification-adjacent siblings such as set_notification_keywords, set_priority_people or set_event_reminders, so an agent must infer that this is per-conversation scope while those are global.

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?

Usage is only implied by the effect described: an agent can deduce it applies when changing one conversation's notification behavior. There is no statement of when not to use it, no prerequisite (e.g. must already be a member of the conversation), and no named alternative for workspace-wide notification preferences.

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