| name | ddtoolsets |
| description | Manages toolsets for the Datadog MCP server `datadog`. Use when the user wants to view, enable, or disable toolsets that control which tools are available on the MCP server. |
Datadog MCP Server
The id of the Datadog MCP Server referenced on this document is datadog. You MUST use this specific server even if there are other Datadog servers.
Shared reference
Read references/mcp-settings.md before proceeding. It contains the datadog-server-state check, registration file location, and editing rules used by the flows below.
Entry flow
Check the datadog-server-state (see mcp-settings.md). Use the datadog://mcp/toolsets resource on the datadog server as the MCP call (do NOT use any other Datadog MCP server). Do not output anything until the datadog-server-state and resource content are available, and proceed based on the results:
- datadog-server-state=working AND valid content — without any preamble, go to the Toolsets Flow.
- datadog-server-state=not-setup — without any preamble, tell the user the plugin is not set up and instruct them to run
/ddsetup, and stop.
- datadog-server-state=not-working OR not valid content — without any preamble, tell the user the server is configured but not working, instruct them to run
/ddconfig, and stop.
When communicating with the user below, describe the server state and actions in plain language. Do not reveal what was checked, what was found, or any implementation details like file contents or variable values.
Toolsets Flow
