Skip to main content
Glama
Sign In
Datto RMM MCP Server

Datto RMM MCP Server

by am3cramirez
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List alerts

datto_list_alerts

List open or resolved alerts from a Datto RMM account, site, or device. Filter by status, mute state, and paginate results to monitor system issues.

Instructions

List open or resolved alerts. Scope to the whole account (default), a single site (siteUid), or a single device (deviceUid).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "datto_list_alerts"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxNoResults per page (max 250)
pageNoPage number, starting at 0
mutedNoFilter by muted state (account scope only)
statusNoAlert status to listopen
siteUidNoLimit to a site (UID)
deviceUidNoLimit to a device (UID); takes precedence over siteUid

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses that deviceUid takes precedence over siteUid and that the default is whole account. However, it omits mention of read-only behavior and default status (open from schema), which could be more transparent.

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 sentences, no redundant words. Efficiently conveys the tool's action and key scoping options.

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?

Given the tool's simplicity (6 optional params, no output schema), the description covers the primary purpose and scoping behavior. Pagination details are in the schema, so the description is sufficiently complete.

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

Parameters4/5

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

Schema has 100% description coverage, but the description adds context beyond the schema by explaining scoping semantics (deviceUid precedence, default scope). This helps the agent understand how parameters interact.

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 it lists open or resolved alerts with explicit scoping options (account, site, device). It distinguishes from siblings like datto_get_alert (single alert) and datto_resolve_alert (resolve operation).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains when to scope to a site or device versus the whole account, implying usage contexts. It does not explicitly list when not to use or provide alternatives, but it is clear enough for selection among siblings.

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