Skip to main content
Glama
Sign In
ESET-MCP

ESET-MCP

by maciekaz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

device_devices__list_devices

Read-onlyIdempotent

Lists managed ESET devices with filtering by display name, mute state, and functionality status, plus pagination to retrieve targeted device inventories.

Instructions

List managed devices - (GET /v1/devices) - List all the managed [device]s.

Input Schema

NameRequiredDescriptionDefault
fieldsNoOptional server-side projection: return only these keys for each list-item in the response. Reduces token usage on large list endpoints. Example: ['uuid','displayName']. Top-level fields (e.g. nextPageToken) are always preserved. Not forwarded to ESET - applied locally after fetch.
isMutedNoIf true, only muted devices will be returned. If false, only not muted devices will be returned. If this field is left empty or not set, the response will return devices, regardless of fact if they are muted or not.
pageSizeNoLimit for pagination purposes. If unspecified or 0, default value is 50. The maximum value is 1000; values above 1000 will be coerced to 1000. > **Info:** > For more information, refer to [Paginating Requests in APIs](https://medium.com/@ignaciochiazzo/paginating-requests-in-apis-d4883d4c1c4c) > > or [Design Patterns: Pagination](https://google.aip.dev/158)
pageTokenNoPage token of the current page. If not given or "", the first page is returned. > **Info:** > For more information, refer to [Paginating Requests in APIs](https://medium.com/@ignaciochiazzo/paginating-requests-in-apis-d4883d4c1c4c) > > or [Design Patterns: Pagination](https://google.aip.dev/158)
displayNamesNoIf populated, devices with `display name` exactly matching one of the strings within the list would be present in the response. If empty, there is no constraint on `display name` of the result set. Example: filter ["Hugo", "Boss"] applied on set ["John", "Boss", "Lemon"] would return devices with display names ["Boss"].
functionalityStatusNoFilter by device functionality status. If this field is filled, the response will include the devices that match the specified functionality status (OK, ATTENTION_RECOMMENDED, or ATTENTION_REQUIRED). If this field is left empty or not set, the response will return devices, regardless of their functionality status. - DEVICE_FUNCTIONALITY_STATUS_UNSPECIFIED: fallback - DEVICE_FUNCTIONALITY_STATUS_OK: The device is functioning normally, with no issues that require attention. - DEVICE_FUNCTIONALITY_STATUS_ATTENTION_RECOMMENDED: There are issues that may not be critical (for example, medium security risks), but they should be addressed to avoid potential future problems. - DEVICE_FUNCTIONALITY_STATUS_ATTENTION_REQUIRED: Critical issues exist (for example, severe security risks), and immediate action is necessary to maintain system integrity or security.DEVICE_FUNCTIONALITY_STATUS_UNSPECIFIED

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds nothing beyond the endpoint path — no note on pagination behavior, default page size, or filtering semantics, which are the behaviors that actually matter for a paged list endpoint.

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?

It is short and front-loaded, but the three dash-separated clauses are highly redundant: the endpoint path and the trailing 'List all the managed [device]s' repeat information already implied by the leading clause. Tightening to one clause plus a routing hint would earn the space better.

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 zero-required-parameter read-only list tool with a fully documented schema and rich annotations, the bar is low, and the description is barely adequate. It omits any routing context to sibling device tools and says nothing about the paged result shape, though the schema covers pagination parameters and there is no output schema.

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 detailed docs for fields, isMuted, pageSize, pageToken, displayNames, and functionalityStatus including an enum explanation. The description contributes no additional parameter meaning, so the baseline of 3 applies.

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 states a clear verb and resource ('List managed devices') and gives the backing REST endpoint, but the third clause 'List all the managed [device]s' merely restates the first. It never distinguishes this tool from close siblings such as device_devices__get_device, batch_get_devices, or device_device_groups__list_member_devices.

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 the many other list/get device tools in the sibling set. The implied usage is 'fetch many devices', but no alternatives, prerequisites, or exclusion conditions are named.

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