Skip to main content
Glama
Sign In
Datto RMM MCP Server

Datto RMM MCP Server

by am3cramirez
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get device software audit

datto_get_device_software

Retrieve a paginated list of audited software installed on a specific device using its UID.

Instructions

List the audited software installed on a device.

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_software"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxNoResults per page (max 250)
pageNoPage number, starting at 0
deviceUidYesDevice UID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It does not mention that the tool returns a paginated list, requires a deviceUid, or that 'audited software' implies a specific scope. Key aspects like pagination behavior are omitted.

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 a single, concise sentence that communicates the core function. It is front-loaded and efficient, though it could include slightly more detail without becoming verbose.

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?

Given the tool has three parameters (including pagination) and no output schema, the description is insufficiently complete. It does not explain the output format, pagination behavior, or what constitutes 'audited software', making it harder for the agent to use correctly.

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?

All three parameters have descriptions in the schema (100% coverage). The description adds no additional meaning beyond what is already in the schema, earning the baseline score of 3.

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 uses a specific verb ('List') and resource ('audited software installed on a device'), clearly indicating the tool's purpose. It differentiates from sibling tools like datto_get_device_audit by focusing specifically on software, though it does not explicitly distinguish itself.

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 is provided on when to use this tool versus alternatives such as datto_get_device or datto_get_device_audit. The description lacks context about prerequisites or typical use cases, leaving the agent to infer from the name and parameters.

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