Datto RMM MCP Server

Set device warranty

datto_set_device_warranty

Set a device's warranty expiration date by providing its UID and the expiration date. Maintain accurate warranty records.

Instructions

Set the warranty expiration date of 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>",
      "warrantyDate": "<warrantyDate>"
    },
    "name": "datto_set_device_warranty"
  }
}

Input Schema

Name	Required	Description	Default
`deviceUid`	Yes	Device UID
`warrantyDate`	Yes	Warranty expiration date (YYYY-MM-DD)

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?

The description only notes 'Set' implying a write operation, but lacks details on behavioral traits such as idempotency, permissions, rate limits, or side effects. With no annotations, the description does little to inform the agent about potential impacts.

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 short sentence with no extraneous information. It is concise, though it could benefit from additional context without losing conciseness. Still, it effectively communicates the core purpose.

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 is a mutation (set operation) with no output schema and no annotations, the description should provide more context about expected behavior, such as whether the date overwrites or appends, error conditions, or response. It is insufficiently complete.

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?

The schema description coverage is 100%, so the schema already documents both parameters. The description adds no additional meaning beyond the schema (e.g., no explanation of valid date ranges or effect on existing warranties). Baseline 3 is appropriate.

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 (set) and the resource (warranty expiration date of a device). It distinguishes from sibling tools like datto_set_device_udf, which handles other device attributes. However, it doesn't explicitly contrast with similar set 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 is provided on when to use this tool versus alternatives. For example, it doesn't mention that datto_set_device_udf could be used for other device settings, or any prerequisites or conditions.

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

Deploy Server