Skip to main content
Glama
Sign In
Datto RMM MCP Server

Datto RMM MCP Server

by am3cramirez
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get job stdout

datto_get_job_stdout

Retrieve the standard output of a job's run on a device using job and device UIDs.

Instructions

Get the standard output of a job's run on a specific 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": {
      "jobUid": "<jobUid>",
      "deviceUid": "<deviceUid>"
    },
    "name": "datto_get_job_stdout"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobUidYesJob UID
deviceUidYesDevice UID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description bears full responsibility for disclosing behavioral traits. It only states the basic action without mentioning any side effects, output format, size limits, or authentication requirements. This is insufficient for an unannotated tool.

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 sentence with no wasted words. It is efficient, though somewhat terse. It could be slightly expanded without losing conciseness.

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 the tool's simplicity (2 parameters, no output schema, no annotations), the description is minimally adequate. It states the tool retrieves stdout for a job run on a device, but does not mention return format or error conditions. More context would be helpful.

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 input schema fully documents both parameters with simple descriptions ('Job UID', 'Device UID'). The description adds no additional meaning or context beyond what is already in the schema, so the baseline score of 3 applies.

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 uses the specific verb 'Get' and explicitly names the resource 'standard output of a job's run on a specific device'. This clearly distinguishes it from siblings like `datto_get_job_stderr` which gets stderr instead.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for retrieving stdout, but provides no guidance on when to use this tool versus alternatives such as `datto_get_job_results` or `datto_get_job_components`. No exclusions or context are given for 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

Other Tools