Skip to main content
Glama
us-all

datadog-mcp-server

by us-all

post-event

Post a custom event to Datadog with markdown and @mentions. Include tags, alert type, priority, host, and aggregation key for monitoring.

Instructions

Post a custom event to Datadog (supports markdown, @mentions)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesEvent title. Example: Deployment completed
textYesEvent body (supports markdown, max 4000 chars). Example: Deployed v1.2.3 to production
tagsNoTags for the event. Example: ["env:prod", "deploy"]
alertTypeNoAlert type
priorityNoEvent priority
hostNoAssociated host name
aggregationKeyNoAggregation key for grouping events
sourceTypeNameNoSource type name. Example: my_app
Behavior2/5

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

With no annotations, the description carries full burden but only mentions markdown/@mention support. It omits essential behavioral traits like idempotency, rate limits, authentication requirements, or whether the event is created synchronously.

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?

One concise sentence front-loads the purpose and key features, with no wasted words.

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 8 parameters, no output schema, and no annotations, the description is insufficient. It fails to explain response format, error handling, or post-creation behavior, leaving the agent with incomplete context.

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 clear parameter descriptions, so baseline is 3. The description adds no extra meaning beyond stating markdown support, which is already implied by the text parameter description.

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?

The description clearly states the verb 'Post' and the resource 'custom event to Datadog', and adds specific features like markdown and @mentions, distinguishing it from sibling tools like get-events.

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 guidance on when to use this tool vs. alternatives, no exclusions, and no mention of prerequisites or context. Sibling tools include many create/update actions, but none for events, so comparison is lacking.

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