Skip to main content
Glama
FouadHELLAL7

Datto EDR MCP Server

by FouadHELLAL7
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

datto_edr_rules_list

Read-only

List Datto EDR detection rules with filters, sorting, pagination, and field selection to review detection coverage and audit rule configurations.

Instructions

List Datto EDR detection rules (GET /api/rules).

Input Schema

NameRequiredDescriptionDefault
nameNoExact rule name
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)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/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 underlying API path (GET /api/rules), which is minor context; nothing is said about pagination behavior or result ordering beyond what the schema hints.

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?

A single short sentence with no waste, and the resource is front-loaded. It is arguably under-specified rather than concise, but nothing is redundant.

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?

The schema is rich and carries all six parameters, and annotations cover the read-only/open-world profile, so the description doesn't need to repeat them. However, for a filterable list tool with a nested LoopBack where object, the description could have noted pagination flow and typical use, which it does not.

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%, with skip/limit/order/where/fields and name all documented in the schema itself, including the LoopBack operator list. The description adds no parameter meaning beyond that, which is the expected baseline when the schema does the work.

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 states a specific verb (List) and a specific resource (Datto EDR detection rules), so the agent knows exactly what comes back. It does not explicitly distinguish the tool from the sibling datto_edr_rules_get, though the list-vs-get naming implies the difference.

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?

There is no guidance on when to use this tool versus datto_edr_rules_get, datto_edr_api_models, or any other sibling. The agent has to infer from the name and schema that this is the paginated collection endpoint.

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