Skip to main content
Glama
us-all

datadog-mcp-server

by us-all

create-synthetics-test

Create a new Synthetics API test to monitor HTTP, SSL, TCP, DNS, and other endpoints with configurable assertions, locations, and alerts.

Instructions

Create a new Synthetics API test (HTTP, SSL, TCP, DNS, etc.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesTest name. Example: API Health Check - Production
typeYesTest type (api)
subtypeNoTest subtype. Example: httphttp
urlYesURL to test. Example: https://api.example.com/health
methodNoHTTP method. Example: GET, POST, PUTGET
locationsYesTest locations. Example: ["aws:us-east-1", "aws:eu-west-1"]
messageNoNotification message. Example: API is down @slack-alerts
tagsNoTags for the test. Example: ["env:prod", "team:platform"]
statusNoInitial test statuspaused
assertionsNoResponse assertions. Example: [{"type":"statusCode","operator":"is","target":200}]
Behavior2/5

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

No annotations are present, so the description carries the full burden. It does not disclose behavioral aspects like required permissions, idempotency, side effects, or execution time. The description only states the action, leaving the agent with no insight into potential pitfalls.

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 a single sentence, front-loading the action and listing examples in parentheses. It is efficient with no wasted words, though brevity sacrifices some clarity on the scope.

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 the tool has 10 parameters, no annotations, and no output schema, the description is too brief. It does not explain return values, configuration nuances, or how it relates to sibling tools like trigger-synthetics or list-synthetics. More context is needed for correct usage.

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 descriptions and examples for all 10 parameters. The description adds no additional meaning beyond the schema; it simply restates the tool's purpose. Baseline score of 3 is appropriate as the schema already does the heavy lifting.

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?

The description states 'Create a new Synthetics API test' and lists protocols like HTTP, SSL, TCP, DNS, etc., clearly indicating the resource and action. It distinguishes from sibling tools like create-monitor or create-downtime, though 'API test' is slightly narrow given the subtypes include non-API protocols.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/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. The usage is implied (when needing to create a synthetics test), but there are no exclusions or prerequisites mentioned. Basic differentiation from trigger-synthetics and update-synthetics-test is possible, but no clear context is provided.

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