Skip to main content
Glama
Sign In
MCP Datadog Server

MCP Datadog Server

by ClaudioLazaro
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

create_dashboards

Build custom Datadog dashboards with configured widgets and queries, including proper metric modifiers for accurate data visualization.

Instructions

Create a dashboard using the specified options. When defining queries in your widgets, take note of which queries should have the as_count() or as_rate() modifiers appended. Refer to the following documentation for more information on these modifiers.

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": "create_dashboards"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/5.0
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 'Create' implies a write operation, the description doesn't mention authentication requirements, permissions needed, rate limits, whether the operation is idempotent, what happens on failure, or what the response contains. The query modifier guidance is useful but doesn't cover core behavioral aspects of a creation operation.

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?

The description is appropriately sized with two sentences. The first sentence states the core purpose, and the second provides specific guidance about query modifiers with a documentation link. There's no wasted text, though the structure could be slightly improved by front-loading the query modifier guidance more clearly.

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?

For a creation tool with no annotations, no output schema, and multiple similar sibling tools, the description is incomplete. It doesn't help the agent understand when to use this versus other dashboard creation tools, what permissions are required, what the response looks like, or error conditions. The query modifier guidance is helpful but insufficient for the overall context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0 parameters and 100% schema description coverage, the baseline is 4. The description adds value by mentioning 'specified options' (impiring some configuration is needed) and providing guidance about query modifiers for dashboard widgets, which gives context about what might be included in those options beyond what the empty schema indicates.

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 'Create a dashboard using the specified options', which clearly indicates the verb (create) and resource (dashboard). However, it doesn't distinguish this from sibling tools like 'create_dashboard_v1', 'create_dashboard_lists_manual_dashboards', or 'create_dashboard_publics', leaving the agent uncertain about which tool to use for different dashboard creation scenarios.

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. With multiple dashboard creation tools in the sibling list (create_dashboard_v1, create_dashboard_lists_manual_dashboards, create_dashboard_publics, etc.), the agent receives no help in selecting the appropriate tool for different use cases. The documentation link about query modifiers is helpful but doesn't address tool selection.

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