Skip to main content
Glama
Sign In
SyncroMSP MCP Server

SyncroMSP MCP Server

by advenimus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

rmm_mute_alert

Mute an RMM alert by providing the alert ID and mute duration. Use 'forever' to permanently silence the alert.

Instructions

Mute an RMM alert. Requires mute_for parameter.

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": {
      "id": "<id>",
      "mute_for": "<mute_for>"
    },
    "name": "rmm_mute_alert"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesAlert ID
mute_forYesMute duration (required). Known valid value: 'forever'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are present, so the description must fully disclose behavioral traits. It only states 'Mute an RMM alert' without explaining side effects (e.g., whether the alert stops notifications, if it's reversible, or any impact on related records). The required mute_for parameter hints at duration but offers no clarity on behavior beyond the action.

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?

The description is very short (two sentences) with no wasted words. It front-loads the action and parameter requirement. However, it could be slightly more informative while remaining concise.

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?

For a simple tool with 2 parameters and no output schema, the description is still under-specified. It fails to explain what 'mute' entails (e.g., effect on alert visibility, notification suppression, or persistence). The required mute_for parameter is mentioned but not elaborated, leaving the agent with insufficient context for proper invocation.

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 100%, so the baseline is 3. The description adds minimal value by repeating 'Requires mute_for parameter' and the known valid value 'forever' (already in schema). No additional semantics provided for either parameter.

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

Purpose5/5

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

The description clearly states the action ('Mute') and the resource ('RMM alert'), making it distinct from sibling tools like rmm_create_alert, rmm_delete_alert, etc. It also mentions the required parameter, leaving no ambiguity about the basic function.

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?

No guidance on when to use this tool vs alternatives (e.g., when to mute vs delete an alert). It only notes the required mute_for parameter but provides no context on prerequisites or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools