Datto RMM MCP Server

Create site

datto_create_site

Create a new site in a Datto RMM account, specifying name, description, and optional settings like on-demand or Splashtop auto-install.

Instructions

Create a new site in the account.

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

Input Schema

Name	Required	Description
`name`	Yes	Site name
`notes`	No	Site notes
`onDemand`	No	Create as an On-Demand site
`description`	No	Site description
`splashtopAutoInstall`	No	Auto-install Splashtop on site devices

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 10, 2026

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 only states 'Create a new site' without mentioning prerequisites (e.g., account existence), idempotency, side effects, or what happens on duplicate names. Minimal transparency for a mutation tool.

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 a single sentence that immediately states the action and resource. Every word is necessary; no fluff. It is efficiently front-loaded.

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 5 parameters and no output schema, the description is too minimal. It does not explain what a 'site' represents, what happens upon creation (e.g., returns an ID), or any behavioral nuances. A more detailed description is needed for a create tool with multiple optional parameters.

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% with descriptions for all 5 parameters. The tool description adds no additional meaning beyond the schema, so baseline score of 3 is appropriate. No new insights are provided.

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 clearly states the action (create) and resource (site) with context (in the account). However, it does not distinguish from sibling tools like datto_create_site_variable or datto_create_account_variable, which create different entities. The specificity is good but lacks differentiation.

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 siblings. For example, there is no mention that datto_update_site is for modifying existing sites, or that datto_list_sites is for viewing existing sites. The description offers no contextual usage advice.

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

Deploy Server