Skip to main content
Glama
brukhabtu

Datadog MCP Server

by brukhabtu

ListRolePermissions

Retrieve all permissions associated with a specific role using the role's unique identifier. Ideal for managing access and verifying role-based privileges in Datadog's observability platform.

Instructions

Returns a list of all permissions for a single role.

Path Parameters:

  • role_id (Required): The unique identifier of the role.

Responses:

  • 200 (Success): OK

    • Content-Type: application/json

    • Response Properties:

      • data: Array of permissions.

    • Example:

{
  "data": [
    "unknown_type"
  ]
}
  • 403: Authentication error

    • Content-Type: application/json

    • Response Properties:

      • errors: A list of errors.

    • Example:

{
  "errors": [
    "Bad Request"
  ]
}
  • 404: Not found

    • 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
role_idYesThe unique identifier of the role.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNoArray of permissions.
Behavior2/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 mentions authentication errors (403), not found (404), and rate limits (429), which adds some behavioral context beyond the basic 'returns a list' purpose. However, it doesn't cover critical aspects like whether this is a read-only operation, what permissions are required, or pagination behavior, leaving significant gaps for a tool with no annotations.

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 overly verbose and poorly structured. It includes extensive HTTP response details (status codes, content types, examples) that belong in an output schema or annotations, not in the description. The core purpose is buried under unnecessary technical documentation, making it inefficient and not front-loaded.

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 has an output schema (implied by context signals) and 100% schema coverage, the description doesn't need to explain return values or parameters in detail. However, it lacks usage guidelines and sufficient behavioral transparency for a tool with no annotations. The inclusion of HTTP response details is redundant with structured fields, making it partially complete but cluttered.

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?

The schema description coverage is 100%, with the input schema fully documenting the single 'role_id' parameter. The description repeats the parameter documentation verbatim ('The unique identifier of the role.'), adding no additional meaning beyond what the schema provides. According to the rules, with high schema coverage, the baseline is 3 even with no extra param info in the description.

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: 'Returns a list of all permissions for a single role.' This is a specific verb ('Returns a list') and resource ('permissions for a single role'). However, it doesn't explicitly differentiate from sibling tools like 'ListUserPermissions' or 'ListRoles', which reduces the score from a perfect 5.

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. It doesn't mention sibling tools like 'ListUserPermissions' or 'GetRole', nor does it specify prerequisites or exclusions. The only implied context is needing a role_id, but this is covered by the input schema.

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