Skip to main content
Glama
Sign In
MCP Datadog Server

MCP Datadog Server

by ClaudioLazaro
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

delete_actions_connection

Remove an existing Action Connection from Datadog to revoke API access permissions and maintain security by eliminating unused integrations.

Instructions

Delete an existing Action Connection. This API requires a registered application key. Alternatively, you can configure these permissions in the UI.

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": "delete_actions_connection"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3/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. It mentions authentication requirements (app key or UI configuration), which is useful behavioral context. However, it lacks critical details: whether deletion is permanent, what happens to associated data, error conditions, or response format. For a destructive operation with zero annotation coverage, this is insufficient.

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 two sentences: the first states the purpose clearly, and the second provides authentication details. It is front-loaded with the core action and avoids unnecessary elaboration. However, the second sentence includes markdown links that might be verbose in some contexts, slightly reducing efficiency.

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?

For a destructive tool with no annotations and no output schema, the description is incomplete. It covers authentication but misses critical context: irreversible nature, side effects, success/error responses, and how to identify the connection to delete. Given the complexity of a delete operation, more behavioral disclosure is needed.

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

Parameters4/5

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

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description does not discuss parameters, which is appropriate. A baseline of 4 is applied since the schema fully covers the absence of parameters, and the description does not introduce confusion.

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 clearly states the action ('Delete') and the resource ('an existing Action Connection'), making the purpose explicit. However, it does not differentiate this tool from other delete operations in the sibling list (e.g., delete_actions_app_key_registration), which would require a 5.

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?

The description provides no guidance on when to use this tool versus alternatives. It mentions authentication requirements but does not specify prerequisites like needing an existing connection ID or when deletion is appropriate compared to other operations like update_actions_connection.

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