Skip to main content
Glama
FouadHELLAL7

Datto EDR MCP Server

by FouadHELLAL7
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

datto_edr_scans_list

Read-only

List Datto EDR scans, optionally for one target group, with pagination, sorting, and filtering to review scan activity.

Instructions

List Datto EDR scans (GET /api/scans), optionally for one target group.

Input Schema

NameRequiredDescriptionDefault
skipNoNumber of results to skip (use nextSkip from the previous page)
limitNoMax results per page (1-1000, default 50)
orderNoLoopBack order, e.g. "createdOn DESC" or "hostname ASC"
whereNoExtra LoopBack where filter, combined with AND, e.g. {"hostname":{"ilike":"%sql%"}}. Operators: eq, neq, gt, gte, lt, lte, between, inq, nin, like, ilike, and, or. Use datto_edr_api_models to see a model's properties.
fieldsNoOnly return these properties (keeps responses small)
target_group_idNoOnly scans of this target group (targetId)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds only the endpoint path and the optional scoping; it says nothing about pagination semantics, result volume, or how skip/limit interact across pages, which are the behaviors that actually matter for a list 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?

A single sentence with zero filler, front-loaded with the verb and resource. Nothing in it is redundant or buried.

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?

For a 6-parameter tool with a nested where filter and no output schema, the description is thin: it does not characterize the returned scan records, pagination flow, or default ordering. The rich schema compensates for most parameter-level gaps, but the description itself does the minimum.

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%, including detailed LoopBack where/order semantics and pagination guidance, so the schema carries the parameter burden. The description only echoes the target_group_id filter, adding no syntax or behavior beyond the structured fields — baseline 3 applies.

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 gives a specific verb and resource ('List Datto EDR scans') plus the backing endpoint (GET /api/scans), which lets an agent separate it from the singular datto_edr_scans_get sibling. It stops short of naming that sibling outright, so the differentiation is implied rather than explicit.

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?

'optionally for one target group' hints at when the filter matters, but there is no statement of when to prefer this over datto_edr_scans_get, datto_edr_target_groups_list, or datto_edr_navigate. Usage is implied by the name and endpoint rather than explained.

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