Skip to main content
Glama
Sign In
Datadog MCP Server

Datadog MCP Server

by dreamiurg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_top_avg_metrics

Retrieve top custom metrics by average hourly count for cost and cardinality analysis for a given month and day. Optionally filter by metric names and paginate results.

Instructions

Get top custom metrics by average hourly count for cost and cardinality analysis

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_top_avg_metrics"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthNo
dayNo
namesNo
limitNo
next_record_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.11.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations provided; description only states purpose without detailing behavioral traits such as pagination (next_record_id), read-only nature, or rate limits. Agent cannot infer important behavior.

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, no unnecessary words; adequate conciseness but could benefit from structured clarity given parameter complexity.

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?

Given complexity of 5 undocumented parameters and no output schema, the description is insufficient for agent to use correctly. Missing parameter semantics and output details.

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

Parameters1/5

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

Input schema has 5 parameters with 0% schema description coverage, and description adds no parameter explanations. Agent lacks guidance on how to use month, day, names, limit, next_record_id.

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 the tool retrieves top custom metrics by average hourly count for cost and cardinality analysis, but does not differentiate from sibling tools like get-metrics, query-metrics, etc.

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 explicit guidance on when to use this tool versus alternatives; lacks context on appropriate scenarios or prerequisites.

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