Skip to main content
Glama
brukhabtu

Datadog MCP Server

by brukhabtu

ListSecurityFilters

Retrieve and review the list of configured security filters along with their definitions to manage and monitor access controls effectively within the Datadog MCP Server environment.

Instructions

Get the list of configured security filters with their definitions.

Responses:

  • 200 (Success): OK

    • Content-Type: application/json

    • Response Properties:

      • data: A list of security filters objects.

    • Example:

{
  "data": [
    "unknown_type"
  ],
  "meta": "unknown_type"
}
  • 403: Not Authorized

    • Content-Type: application/json

    • Response Properties:

      • errors: A list of errors.

    • Example:

{
  "errors": [
    "Bad Request"
  ]
}
  • 429: Too many requests

    • Content-Type: application/json

    • Response Properties:

      • errors: A list of errors.

    • Example:

{
  "errors": [
    "Bad Request"
  ]
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNoA list of security filters objects.
metaNo
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It adds value by detailing HTTP response codes (200, 403, 429) with examples, which helps the agent understand success and error conditions. However, it lacks critical behavioral details like authentication requirements, rate limits, pagination, or whether the operation is read-only (implied by 'Get' but not explicit).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is poorly structured and verbose. It front-loads the purpose clearly but then dedicates excessive space to HTTP response examples (including full JSON snippets), which could be summarized or omitted if an output schema exists. The content is not efficiently organized, with redundant details that don't add proportional value.

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?

Given the tool's simplicity (0 parameters, output schema exists), the description is moderately complete. It covers the basic purpose and response behaviors, but with no annotations and sibling tools present, it should ideally clarify distinctions and usage context. The output schema reduces the need to explain return values, but the description still lacks guidance on when to use this tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0 parameters with 100% description coverage, so the schema fully documents the absence of inputs. The description doesn't need to add parameter details, but it correctly implies no required inputs by focusing on responses. A baseline of 4 is appropriate since there are no parameters to explain.

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 clearly states the tool's purpose: 'Get the list of configured security filters with their definitions.' This specifies the verb ('Get'), resource ('security filters'), and scope ('list' with 'definitions'). However, it doesn't explicitly differentiate from sibling tools like 'GetSecurityFilter' (singular vs. plural), which could cause confusion about when to use each.

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?

The description provides no guidance on when to use this tool versus alternatives. With sibling tools like 'GetSecurityFilter' (singular) and 'ListSecurityMonitoringRules' (similar listing pattern), there's no indication of whether this tool is for bulk retrieval, filtering options, or specific use cases. The absence of usage context leaves the agent without direction.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/brukhabtu/datadog-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server