Skip to main content
Glama
us-all

datadog-mcp-server

by us-all

list-hosts

List and filter infrastructure hosts by tag or environment, sort by metrics like CPU or load, and retrieve metadata such as agent version, platform, and mute status.

Instructions

List infrastructure hosts with filtering, sorting, and metadata

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filterNoFilter string for search results. Example: web-server or env:prod
sortFieldNoField to sort by. Example: apps, cpu, iowait, load
sortDirNoSort direction: asc or desc
countNoNumber of hosts to return (max 1000)
startNoPagination offset
fromNoUnix epoch seconds — hosts active since this time. Example: 1740000000
includeMutedHostsDataNoInclude mute status info
includeHostsMetadataNoInclude agent_version, machine, platform, processor
Behavior2/5

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

Description gives high-level behavior but does not disclose read-only nature, permissions, pagination limits (max 1000 from schema), or potential side effects. Without annotations, the description fails to provide necessary behavioral context.

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?

Single sentence that is direct and front-loaded. No superfluous information.

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?

Despite multiple parameters, the description does not explain usage patterns (e.g., how filtering or sorting works), pagination behavior, or output format. Lacks completeness for a tool with 8 parameters and no output schema.

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 covers 100% of parameters with descriptions. The high-level grouping in description (filtering, sorting, metadata) adds marginal value beyond the schema, so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clear verb (List) and resource (infrastructure hosts), includes key features (filtering, sorting, metadata). Distinct from sibling tools that list other resources.

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 vs alternatives like get-host-totals or list-services. Does not mention prerequisites or exclusion criteria.

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

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/us-all/datadog-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server