Skip to main content
Glama
Sign In
Datto RMM MCP Server

Datto RMM MCP Server

by am3cramirez
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get device audit

datto_get_device_audit

Retrieve complete audit data for a device, including hardware, OS, network, disks, and installed patches. Use a device UID to access detailed device information.

Instructions

Get the full audit data of a device (hardware, OS, network, disks, installed patches, etc.).

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": {
      "deviceUid": "<deviceUid>"
    },
    "name": "datto_get_device_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceUidYesDevice UID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, description carries full burden. It indicates a read operation ('get') and specifies the data returned, but lacks details about side effects, rate limits, or authentication requirements. Adequate but not thorough.

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?

Single sentence with no wasted words. Directly conveys purpose and scope of data.

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?

For a simple tool with one parameter and no output schema, the description is sufficiently complete. It explains what the tool returns, meeting the needs for selection and 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% and defines the single parameter. Description does not add further meaning to the parameter beyond what the schema provides (Device UID). Baseline of 3 applies.

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?

Description clearly states the verb 'get' and resource 'audit data of a device', and lists specific categories (hardware, OS, network, disks, installed patches). This effectively distinguishes it from sibling tools that retrieve other device-related data.

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 versus alternatives. Does not provide context for when to use datto_get_device_audit vs. datto_get_device or other audit tools.

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