Skip to main content
Glama
Sign In
Datadog MCP Server

Datadog MCP Server

by peterlozano
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_host_totals

Retrieve total counts of active and up hosts in Datadog, optionally filtered by a time window, to monitor host availability.

Instructions

Get total counts of active and up hosts in Datadog.

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

Input Schema

NameRequiredDescriptionDefault
fromNoOnly count hosts alive since this time2h

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/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. It states the high-level output but does not mention read-only safety, permissions, rate limits, side effects, or return format.

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

Conciseness5/5

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

A single concise sentence that is front-loaded with the action and resource. There is no wasted wording, making it appropriately sized for the amount of information provided.

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?

For a simple read-only count tool with no annotations or output schema, the description is minimally adequate. However, it omits important context such as the time-window behavior implied by the 'from' parameter and the structure of the returned counts.

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% for the single 'from' parameter, so the schema already documents it fully. The description adds no additional meaning or format details beyond what the schema provides, making the baseline 3 appropriate.

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?

States a specific verb and resource: 'Get total counts of active and up hosts in Datadog.' Clear on what it does, but does not distinguish itself from the sibling list_hosts tool, which also deals with hosts.

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?

Gives no guidance on when to use this tool versus alternatives such as list_hosts. There is no context about when a count is preferable to a full host listing.

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