Skip to main content
Glama
brukhabtu

Datadog MCP Server

by brukhabtu

ListUserOrganizations

Retrieve user information and associated organizations by providing the user ID. This tool helps identify and manage user-organization relationships within the Datadog MCP Server.

Instructions

Get a user organization. Returns the user information and all organizations joined by this user.

Path Parameters:

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

Responses:

  • 200 (Success): OK

    • Content-Type: application/json

    • Response Properties:

      • included: Array of objects related to the user.

    • Example:

{
  "data": "unknown_type",
  "included": [
    "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
dataNo
includedNoArray of objects related to the user.
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 of behavioral disclosure. While it mentions authentication errors (403) and rate limits (429), it lacks details on permissions required, whether the operation is read-only or mutative, response formats beyond basic examples, or pagination behavior. For a tool with no annotation coverage, this is insufficient.

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 redundant parameter details (already in the schema) and extensive HTTP response documentation that belongs in an output schema. The core purpose is buried under technical details, making it inefficient for quick understanding by an AI agent.

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 the detailed response documentation) and 100% schema coverage, the description is somewhat complete but inefficient. It covers basic purpose and error cases but lacks behavioral context like permissions or usage guidelines. The redundancy with structured data reduces its effectiveness.

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 a 'Path Parameters' section but adds no additional meaning, syntax, or format details beyond what the schema provides. This meets the baseline 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 organization' and specifies it returns 'user information and all organizations joined by this user.' This is a specific verb+resource combination. However, it doesn't distinguish from sibling tools like 'GetUser' or 'ListUsers,' which reduces the score from a 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 'GetUser' or 'ListUsers,' nor does it specify prerequisites, exclusions, or appropriate contexts for usage. This leaves the agent without clear decision-making criteria.

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