Datto RMM MCP Server

Create site variable

datto_create_site_variable

Create a site variable to store key-value data within a Datto RMM site, with optional masking for sensitive values.

Instructions

Create a variable in a site.

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": {
      "siteUid": "<siteUid>",
      "name": "<name>",
      "value": "<value>"
    },
    "name": "datto_create_site_variable"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Variable name
`value`	Yes	Variable value
`masked`	No	Mask (hide) the value in the UI
`siteUid`	Yes	Site UID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 10, 2026

TDQS

C2.5/5.0

Behavior2/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 states 'Create' implying mutation, but does not disclose any side effects, permissions, or reversibility. This is insufficient 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.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single short sentence, which is concise but borderline under-specified. It lacks any structured breakdown of behavior, which would improve usefulness.

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?

The description covers the bare minimum. With no output schema and no annotations, it does not explain return values, error conditions, or behavior beyond creation. For a tool with 4 parameters, this is incomplete.

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%, and the schema's property descriptions are adequate. The tool description adds no additional meaning beyond what is already in the schema, so a baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Create a variable in a site' clearly identifies the action and resource, but it is generic and does not differentiate from sibling tools like datto_create_account_variable. The purpose is vague given the many similar create tools.

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 such as datto_create_account_variable. No context about prerequisites or exclusions, leaving an agent to infer usage from the name and schema alone.

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

Deploy Server