Skip to main content
Glama
brukhabtu

Datadog MCP Server

by brukhabtu

GetUser

Retrieve user details within an organization by specifying the user's ID. Supports JSON responses for success, authentication errors, and request limits.

Instructions

Get a user in the organization specified by the user’s user_id.

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.
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 includes response details (e.g., 200, 403, 404, 429) which adds context on error handling and rate limiting, but lacks information on authentication requirements, permissions, or side effects, making it incomplete 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 and poorly structured, with extensive HTTP response details that clutter the core purpose. It includes redundant information (e.g., repeating parameter details) and lacks front-loading of key information, making it inefficient for quick comprehension.

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) and the presence of an output schema (implied by response details), the description is mostly complete. It covers the basic operation and error cases, but could improve by integrating with sibling tools or clarifying behavioral aspects, keeping it from a score of 5.

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 schema. The description repeats this information without adding extra meaning or context, such as format examples or usage tips, so it meets the baseline but doesn't enhance understanding.

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 in the organization specified by the user's `user_id`.' It uses a specific verb ('Get') and identifies the resource ('a user'), but does not distinguish it from sibling tools like 'ListUsers' or 'GetUserMemberships', which is why it doesn't reach a score 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 sibling tools like 'ListUsers' for listing multiple users or 'GetUserMemberships' for related data, nor does it specify prerequisites or exclusions, leaving the agent without usage context.

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