Skip to main content
Glama

Coline

Set notification keywords

set_notification_keywords
DestructiveIdempotent

Replaces the words that notify the person whenever someone writes them.

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>",
      "rules": "<rules>"
    },
    "name": "set_notification_keywords"
  }
}

Input Schema

NameRequiredDescriptionDefault
rulesYes
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is known; the description's "Replaces" corroborates the wipe-and-replace behavior, which is genuinely useful context. It does not add anything on permissions, whose keywords are affected ("the person" is ambiguous), whether an empty list clears all keywords, or the 50-item cap.

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?

A single short sentence with the most important fact (replacement) front-loaded and no filler. Its brevity comes at the cost of specificity, but nothing is padded or redundant.

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

Completeness2/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 no explanation, but this is a destructive bulk-replace mutation over a nested rules array with four undocumented sub-fields. The definition omits clearing behavior, the item limit, and who the notification target is, leaving real ambiguity for a call that overwrites existing configuration.

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 coverage is only 50% — the workspace slug is documented, but the rules array's keyword, caseSensitive, wholeWord, and enabled fields carry no descriptions. The description says nothing about any parameter, so it does not compensate for the coverage gap; only the field names themselves hint at meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Replaces" is a more precise verb than the title's "Set" and it does convey full-replacement semantics for a notification trigger. But the resource is described only metaphorically as "the words that notify the person," never naming keywords, notification rules, or the user/workspace scope, and nothing distinguishes it from siblings like set_conversation_notifications.

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?

There is no explicit when-to-use or when-not-to-use guidance and no alternative tool is named. The only implicit signal is that this overwrites rather than appends, which the agent must infer from the word "Replaces."

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