Retrieve available filter options for a specific XDR section, including alerts, incidents, files, and audit, to construct targeted queries and searches.
Get available filter options for an XDR section.
| Name | Required | Description | Default |
|---|---|---|---|
| section | Yes | Section name, one of: alerts, incidents, emails, files, events, connections, assets, modules, audit, applications, application_versions |
Changes observed during successful MCP inspections.
v1.3.0Input schema / properties / section / descriptionPrevious value: -"Section name, one of: alerts, incidents, emails, files, events, connections, assets, modules, audit, applications"New value: +"Section name, one of: alerts, incidents, emails, files, events, connections, assets, modules, audit, applications, application_versions"Input schema / properties / section / enumPrevious value: -[
- "alerts",
- "incidents",
- "emails",
- "files",
- "events",
- "connections",
- "assets",
- "modules",
- "audit",
- "applications"
-]New value: +[
+ "alerts",
+ "incidents",
+ "emails",
+ "files",
+ "events",
+ "connections",
+ "assets",
+ "modules",
+ "audit",
+ "applications",
+ "application_versions"
+]v0.1.0Does 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 that the result is a set of available filter options (metadata, not records), but says nothing about result shape, whether options are static per section, or whether they reflect live tenant state.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence with zero filler. It is efficient, though the brevity leaves gaps that other dimensions penalize.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
This is a low-complexity, one-parameter discovery tool, so the description is close to sufficient for correct invocation. However, with no output schema, an agent gets no hint about the shape of the returned filter options, which is the main thing missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and the single 'section' parameter carries a full enum with a matching description, so the schema does the work. The description adds no meaning beyond that, such as how section choice changes the returned option set.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description names a specific verb ('Get') and resource ('available filter options for an XDR section'), so an agent can tell it retrieves filter metadata rather than data. It does not differentiate itself from siblings such as xdr_get_suggestions or xdr_get_mapping, which could plausibly return similar-looking option lists.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no when-to-use guidance, no prerequisite (e.g., call before xdr_search to discover valid filter values), and no mention of when to prefer xdr_get_suggestions or xdr_get_mapping instead. The usage is only inferable from the phrase 'filter options'.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.