Skip to main content
Glama
brukhabtu

Datadog MCP Server

by brukhabtu

GetUserMemberships

Retrieve a user's team memberships by providing their UUID, enabling efficient management of user associations within Datadog's observability platform through structured API responses.

Instructions

Get a list of memberships for a user

Path Parameters:

  • user_uuid (Required): None

Responses:

  • 200 (Success): Represents a user's association to a team

    • Content-Type: application/json

    • Response Properties:

      • data: Team memberships response data

      • included: Resources related to the team memberships

    • Example:

{
  "data": [
    "unknown_type"
  ],
  "included": [
    "unknown_type"
  ],
  "links": "unknown_type"
}
  • 404: API error response.

    • 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_uuidYesNone

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNoTeam memberships response data
metaNo
linksNo
includedNoResources related to the team memberships
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 mentions HTTP responses (200, 404, 429) with error details, which adds useful behavioral context like rate limiting and error handling. However, it doesn't disclose other traits such as authentication requirements, pagination, or data freshness, which are important for a read operation.

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, including detailed HTTP response examples and properties that belong in an output schema. The core purpose is buried under technical details, making it less front-loaded and efficient. Sentences like 'Represents a user's association to a team' are redundant with the title, reducing conciseness.

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 that an output schema exists (implied by context signals), the description doesn't need to explain return values in detail. However, for a tool with no annotations and one parameter, it provides some behavioral context (e.g., error responses) but lacks completeness in usage guidelines and transparency about operational aspects like permissions or limits.

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 the parameter 'user_uuid' documented in the schema as a required string. The description repeats this as a path parameter but adds no additional meaning (e.g., format examples or source of the UUID). Since the schema already covers it adequately, the baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Get a list of memberships for a user', which clearly indicates a read operation on user-team associations. However, it's somewhat vague about what 'memberships' specifically entail (e.g., team roles, permissions) and doesn't differentiate from sibling tools like GetUser or ListUserOrganizations, which might overlap in functionality. The purpose is understandable but lacks specificity.

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?

No guidance is provided on when to use this tool versus alternatives. Sibling tools include GetUser, ListUserOrganizations, and ListRoleUsers, which might retrieve related user data, but the description doesn't clarify distinctions or prerequisites. This leaves the agent without context for tool selection.

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