Skip to main content
Glama
Sign In
Datadog MCP Server

Datadog MCP Server

by dreamiurg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get-powerpacks

Retrieve reusable dashboard widget templates (Powerpacks) to apply pre-built configurations for monitoring dashboards.

Instructions

Get reusable dashboard widget templates (Powerpacks)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get-powerpacks"
  }
}

Input Schema

NameRequiredDescriptionDefault
page_limitNoMaximum number of results
page_offsetNoPage offset

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.11.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations provided, so description must disclose behavior. It only says 'Get', implying a read operation, but does not confirm read-only behavior, pagination details, permissions needed, or the form of the result. Minimal transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence, front-loaded with verb and resource. No fluff, but could provide slightly more detail without losing conciseness. Efficient.

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

Completeness2/5

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

Tool is simple with 2 params and no output schema. Description explains what it fetches but not the return format (list of objects?), pagination behavior, or how results are ordered. Leaves questions for the agent.

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 coverage is 100%, with both page_limit and page_offset described. The description adds no extra meaning beyond the schema. Baseline 3 is appropriate since schema fully documents parameters.

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?

Description clearly states verb 'Get' and resource 'reusable dashboard widget templates (Powerpacks)'. It distinguishes from sibling tools as no other powerpack-related tool exists. However, it could elaborate on what a Powerpack is (e.g., a dashboard template).

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 on when to use this tool vs alternatives. No mention of prerequisites, filtering, or context where this might be preferred over other get/list tools. The description solely explains what it does without usage context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools