Skip to main content
Glama
Sign In
ESET-MCP

ESET-MCP

by maciekaz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

incident_edr_rules__list_edr_rules

Read-onlyIdempotent

Retrieve EDR rules matching specified criteria, with optional severity filtering, pagination, field projection, and total-size inclusion for focused results.

Instructions

List EDR rules - (GET /v2/edr-rules) - List [EDR rule]s matching the criteria.

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.
pageSizeNoLimit for pagination purposes. If unspecified or 0, the 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)
severityLevelNoIf filled, only the rules with matching `severity_level` will be included in the response. - SEVERITY_LEVEL_UNSPECIFIED: fallback - SEVERITY_LEVEL_DIAGNOSTIC: In some GUIs known `Debug` - SEVERITY_LEVEL_INFORMATIONAL: In some GUIs known as `Info` or `Information` - SEVERITY_LEVEL_LOW: In some GUIs known `Warning` - SEVERITY_LEVEL_MEDIUM: In some GUIs known as `Error` or `Threat` - SEVERITY_LEVEL_HIGH: In some GUIs known as `Critical`SEVERITY_LEVEL_UNSPECIFIED
includeTotalSizeNoIf true, the `total_size` attribute is filled in the response.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered. The description adds essentially nothing beyond re-stating the operation and its HTTP path, saying nothing about pagination defaults, projection behavior, or result volume that is not already covered elsewhere.

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?

Two short clauses, front-loaded with the verb and resource, with no padding. The bracketed '[EDR rule]s' formatting is an artifact and the repeated endpoint segment is mild redundancy, but nothing is bloat.

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 five-parameter, fully optional list endpoint with a rich schema, the description is minimally adequate but omits how to page through results or that filters are optional server-side. An agent must fall back on the schema to learn that pagination and projection exist.

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 pageSize, pageToken, fields, severityLevel (including enum semantics and GUI aliases) and includeTotalSize. The description adds no parameter meaning of its own, so the baseline of 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?

States a specific verb and resource ('List EDR rules') and includes the underlying endpoint, which cleanly separates it from the sibling get_edr_rule. It does not, however, name any sibling or scope the result set beyond 'matching the criteria'.

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 explicit when-to-use guidance, no mention of when not to use it, and no reference to alternatives such as get_edr_rule or list_edr_rule_exclusions. The phrase 'matching the criteria' only hints that filtering exists, without saying which filters matter or when to prefer this listing over a direct get.

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