Skip to main content
Glama
brukhabtu

Datadog MCP Server

by brukhabtu

ListUserPermissions

Retrieve a user's permission set from the Datadog MCP Server by providing their user ID. Returns a list of permissions granted by their roles.

Instructions

Get a user permission set. Returns a list of the user’s permissions granted by the associated user's roles.

Path Parameters:

  • user_id (Required): The ID of the user.

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
user_idYesThe ID of the user.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNoArray of permissions.
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It adds value by detailing error responses (403, 404, 429) and the success response format, which helps the agent understand potential failures and output structure. However, it lacks information on rate limits, pagination, or caching behavior, leaving gaps in operational context.

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 for an MCP tool definition. It includes extensive HTTP response details (status codes, content types, examples) that are redundant with structured output schemas. The core purpose is buried among technical specifications, making it less front-loaded and efficient for an AI agent.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's low complexity (1 parameter, no nested objects) and the presence of an output schema (implied by response details), the description is reasonably complete. It covers the purpose, parameter, and response formats, though it could benefit from more behavioral context like authentication needs. The output schema reduces the need for detailed return value explanations.

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 parameter 'user_id' fully documented in the input schema. The description repeats the parameter information in the 'Path Parameters' section but adds no additional semantic context beyond what the schema provides. This meets the baseline of 3 for high schema coverage.

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 a user permission set' with the specific action 'Returns a list of the user's permissions granted by the associated user's roles.' This distinguishes it from sibling tools like 'GetUser' or 'ListRolePermissions' by focusing on permission retrieval rather than user details or role-specific permissions. However, it doesn't explicitly differentiate from all siblings in the list, keeping it at 4 instead of 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 prerequisites, such as authentication requirements implied by the 403 error, or compare it to similar tools like 'ListRolePermissions' or 'GetUserMemberships'. The agent must infer usage from context alone.

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