Datto RMM MCP Server

List components

datto_list_components

Retrieve a paginated list of automation components (scripts) from your Datto RMM account. Component UIDs are used to run quick jobs.

Instructions

List the account's components (scripts/automation components). Use a component's UID with datto_run_quickjob.

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

Input Schema

Name	Required	Description	Default
`max`	No	Results per page (max 250)
`page`	No	Page number, starting at 0

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 10, 2026

TDQS

A3.9/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 full burden. It indicates a read operation ('list') but does not disclose additional behavioral traits such as authentication requirements, rate limits, or pagination details. The schema shows pagination parameters, but the description does not elaborate on the behavior.

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?

The description is extremely concise with two sentences. The first sentence states the purpose, and the second provides a usage reference. No extraneous information is present, making it efficient for an agent to parse.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given that there is no output schema, the description could have elaborated on the return structure or content. It only mentions listing components but does not specify what fields are returned (e.g., UID, name). While the input schema is complete, the output is left unspecified, which may cause ambiguity for the agent.

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 description coverage is 100%, with both parameters having clear schema descriptions (max and page). The tool description adds no further meaning beyond what the schema already provides. Baseline 3 is appropriate given the high schema coverage.

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 the account's components (scripts/automation components), using the verb 'list' and specifying the resource. It also distinguishes itself from siblings by being specifically for components and hints at a common follow-up action with datto_run_quickjob.

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 provides guidance by mentioning that a component's UID can be used with datto_run_quickjob, implying a typical workflow. However, it does not explicitly state when to use this tool versus other list tools (e.g., datto_list_filters) or when not to use it.

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

Deploy Server